[Koha-devel] Koha Foundation Proposal

[Brendan Gallagher via Koha-devel]

Hello All - Good day to everyone!

At the Koha Community Hackfest held in Marseille, France on 8th - 12th
April 2024 community members once again raised the topic of governance and
sustainability of Koha. Prior to that meeting Brendan Gallagher and
Jonathan Field had done some background work to look into the prospect of
putting the Koha project into a foundation. Although this is something that
members of the community have explored previously, the feeling is now that
the landscape has changed and it’s a good time to revisit this topic.

There are numerous benefits of moving Koha into a Foundation for the long
term sustainability of this Open Source Project. Koha is a mature, very
large project and represents 177 years of collective work (hours) of
development time (https://openhub.net/p/koha). First of all we think
everyone should stand up and celebrate that fact - this project is
Awesome!  One of the big advantages of putting Koha into a foundation is
that we can start to have a more formalised governance structure - which
will improve our communication and our development processes. In addition,
we will be protecting Koha for future generations to come.

Part of the exploratory work involved talking to some community members,
support organisations, non-library specific foundations, and looking
at the Open
Library Foundation <https://openlibraryfoundation.org/> (OLF). This
included talking to an open source project (VuFind
<https://vufind.org/vufind/>) that has recently joined OLF, as well as a
discussion with the current President of OLF (Tom Cramer
<https://openlibraryfoundation.org/about/leadership/>).

We presented this work to the Hackfest on 10th April 2024 to the assembled
gathering. There was a large consensus for the need of a foundation and
that OLF would be a good home for Koha. There was a request that we hold a
vote to include a wider audience of Koha libraries, community members, and
support organisations in the decision. We would therefore like to submit
the following proposal:

“Open Library Foundation (OLF) should become the home for creating a new
Koha Foundation spot.  The structure of the OLF is that each project
establishes its own legal identity where each project can create governance
models that fit for their open source project, establish banking accounts
for fund raising and supporting community focused programs, allow for
consolidated technology resources (website, bug tracker, mailing list
forums, etc.), and have legal advice/practice available to support and
protect the project.”

Before putting this proposal to a vote, we would like to leave a window of
opportunity to ask questions and discuss. We have included the background
and research that we did, please take a look at the document (attached).
Once you have digested this information please feel free to discuss via
IRC, post questions to the Koha mailing lists or join the new chat facility
at https://chat.koha-community.org/. There is also a Koha community meeting
on the 15th May
<https://wiki.koha-community.org/wiki/Development_IRC_meeting_15_May_2024>where
any questions can be answered.

Alternatively, contact bren...@bywatersolutions.com or
jonathan.fi...@ptfs-europe.com who would be happy to take any questions you
may have.

After a period of discussion, we will send out a link to a vote. We would
request that as many members of this community who have an interest in the
future of Koha participate in this vote.

Cheers and thank you,
Brendan and Jonathan


-- 
---
Brendan A. Gallagher

bren...@bywatersolutions.com 

Follow us:
<https://www.facebook.com/ByWaterSolutions/>
<https://www.instagram.com/bywatersolutions/>
<https://www.youtube.com/user/bywatersolutions>
<https://twitter.com/ByWaterSolution>


Koha Foundation proposal .pdf
Description: Adobe PDF document
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Koha 23.05 released

[Brendan Gallagher]

Congratulations!

On Wed, May 31, 2023 at 1:19 PM DevinimKoha 
wrote:

> Congratulations and thanks to everyone!
> On 31.05.2023 22:49, Tomas Cohen Arazi wrote:
>
> The Koha community is proud to announce the release of Koha 23.05.00.
>
> Koha 23.05.00 is a major release, that comes with many new features.
>
> It includes 26 new features, 145 enhancements, 701 bugfixes.
>
> The full release notes are available here:
> https://koha-community.org/koha-23-05-released/
>
> Debian packages should be available soon
>
> Best regards
>
> --
> Tomás Cohen Arazi
> Theke Solutions (http://theke.io)
> ✆ +54 9351 3513384
> GPG: B2F3C15F
>
> ___
> Koha-devel mailing 
> listkoha-de...@lists.koha-community.orghttps://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>


-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Office: Portland, OR - Office: Trumbull, CT
Phone # (888) 900-8944
https://bywatersolutions.com 
bren...@bywatersolutions.com 

Follow us:




___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] KohaCon18 Portland, Oregon Air Quality

[Brendan Gallagher]

As of about 16:00 yesterday we are in the Good air quality section!

On Wed, Aug 22, 2018 at 6:41 PM, Eric Bégin  wrote:

> I'm sure Kohacon will bring a breath of fresh air :-)
>
> Eric Bégin
> Solutions inLibro inc.
> Le 22 août 2018, à 21:35, David Cook  a écrit:
>
>> Hi all,
>>
>>
>>
>> I don’t know why it’s just occurred to me to mention it now, but with
>> Kohacon coming up quite soon, it’s worth keeping an eye on the air quality
>> and planning ahead: https://airnow.gov/index.cfm?
>> action=airnow.local_city=160.
>>
>>
>>
>> At the moment, it’s rated as “Unhealthy” with a health message of “Health
>> Message: People with heart or lung disease, older adults, and children
>> should avoid prolonged or heavy exertion. Everyone else should reduce
>> prolonged or heavy exertion.”
>>
>>
>>
>> Here’s hoping that the air quality improves in the next couple of weeks.
>> I think the air quality has been bad for a couple of weeks now already, but
>> again Brendan would have the best info about this.
>>
>>
>>
>> David Cook
>>
>> Systems Librarian
>>
>> Prosentient Systems
>>
>> 72/330 Wattle St
>> 
>>
>> Ultimo, NSW
>> 
>> 2007
>>
>> Australia
>>
>>
>>
>> Office: 02 9212 0899
>>
>> Direct: 02 8005 0595
>>
>>
>>
>> --
>>
>> Koha-devel mailing list
>> Koha-devel@lists.koha-community.org
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>>
>>


-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Office: Portland, OR - Office: Redding, CT
Phone # (888) 900-8944
https://bywatersolutions.com 
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] KohaCon18 social stuff

[Brendan Gallagher]

The air quality here right now is not good at all.  It should definitely be
cleared out of here in a couple of weeks though.  I'll keep updating on
that weekly.

On Wed, Aug 22, 2018 at 6:27 PM, David Cook 
wrote:

> Looks like Chris added Cascade Brewing for 10 September. It's top of my
> list of beer places to explore in Portland, although I have another 20
> suggestions from beer people I know, plus I'm sure Brendan must have
> suggestions, so I think there are no shortage of options there.
>
> Actually, important FYI for KohaCon18 attendees... there are a lot of
> wildfires in the Pacific Northwest at the moment, so the air quality is
> quite low. Brendan would have the best insight on that one as a local, but
> I have friends and family in western North America who are requiring air
> purifiers indoors and masks outdoors, so worth keeping in mind for your
> visit (and your planning of outdoor activities), especially if you have
> health problems like asthma or other respiratory issues.
>
> David Cook
> Systems Librarian
> Prosentient Systems
> 72/330 Wattle St
> Ultimo, NSW 2007
> Australia
>
> Office: 02 9212 0899
> Direct: 02 8005 0595
>
>
> -Original Message-
> From: koha-devel-boun...@lists.koha-community.org [mailto:
> koha-devel-boun...@lists.koha-community.org] On Behalf Of Paul Poulain
> Sent: Thursday, 23 August 2018 2:15 AM
> To: koha-devel@lists.koha-community.org
> Subject: [Koha-devel] KohaCon18 social stuff
>
> Hello,
>
> Just for those who are not following wiki closely :
> https://wiki.koha-community.org/wiki/Kohacon18/Social
>
> => you can register here your arrival & departure infos
>
> => you can see some ideas trip trip/beer/fun/...
>
> --
> Paul Poulain, Associé-gérant / co-owner
> BibLibre, Services en logiciels libres pour les bibliothèques BibLibre,
> Open Source software and services for libraries
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/ git :
> http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
>
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Office: Portland, OR - Office: Redding, CT
Phone # (888) 900-8944
https://bywatersolutions.com 
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Koha Core anyone?

[Brendan Gallagher]

Very excited by this idea.  Lot's to think about.  We're on board with most
of it and are ready to help.

Cheers,
Brendan

On Tue, Apr 10, 2018 at 9:30 AM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Ha, found it!
> https://gitlab.deichman.no/digibib/Koha/commits/circ_rewrite_master
> I was looking at the digibib github repo!
>
>
> On Tue, 10 Apr 2018 at 13:28 Jonathan Druart  community.org> wrote:
>
>> Hi Benjamin,
>>
>> Where is the code of the "working example"?
>>
>> Cheers,
>> Jonathan
>>
>> On Tue, 10 Apr 2018 at 12:04 Benjamin Rokseth <
>> benjamin.roks...@deichman.no> wrote:
>>
>>> Community hackers,
>>>
>>> on hackfest I got introvertly enthusiastic about the concept of a Koha
>>> Core, and
>>> about time I shared some thoughts.
>>>
>>> Background: Deichman (Oslo Public Library) is heavily leaning on
>>> bleeding edge Koha
>>> development (REST, Objects, Auth, NCIP and such) and, like at least some
>>> others, maintain
>>> a lot of local patches to tweak Koha into our users needs. Some are
>>> probably interesting to
>>> Community, others not. Now to keep everything in sync with Community
>>> would be amazing,
>>> but not likely to happen anytime soon.
>>>
>>> Great work has been done on refactoring Koha (new namespace, Koha
>>> Objects and REST api, etc.),
>>> but we'd like to suggest one more - a Koha core.
>>> The idea is simple: borrow from object oriented languages, java, or
>>> actually more ruby, since
>>> we're dealing with a dynamic language, use class/module inheritance and
>>> method overrides.
>>> Perl has the "use parent" concept which simplifies
>>> inheritance/subclassing and allows for
>>> nested overrides.
>>>
>>> As an example we refactored the current circulation in Koha, since this
>>> for us is the core
>>> functionality that we depend on and need to hook our local quirks on top
>>> of.
>>> An attempt to illustrate:
>>>
>>> ++
>>> | Core::Main |
>>> +--^-+
>>>|
>>> +--++
>>> | Core::Prefs   |
>>> | Core::Exceptions  |+---+
>>> | Core::Circulation <-+--+---| Deichman::Circulation |
>>> | ...   | |  |   +---^---+
>>> +---+ |  |   |
>>>   |  |   |
>>>+--+--+   +--+
>>>| Core::Circulation::SIP  |   |Deichman::Circulation::SIP|
>>>++
>>>  |use parent qw(
>>>  |  Deichman::Circulation
>>>   +--+  Core::Circulation::SIP
>>>   | Core::Circulation::UI|)
>>>   +--+
>>>  |
>>>  ~
>>>
>>> * Core::Main is simply an empty class that act as a parent for any
>>> child, including Core::Circulation.
>>> * Core::Circulation has a constructor that takes koha objects item and
>>> library, optionally patron
>>>   and sysprefs overrides. It can have accessors such as checkout,
>>> messages and other things needed for
>>>   intra, SIP or whatever. It has methods Checkin, Checkout and Renew,
>>> amongst others.
>>> * then: Deichman::Circulation::SIP in this example is a local override
>>> that inherits from parents
>>>   Deichman::Circulation and Core::Circulation::SIP
>>>
>>> now the beauty of this is that Deichman::Circulation::SIP can override
>>> anything (even the constructor)
>>> without touching any of the core code, and perl will traverse the
>>> inheritance tree until it finds the
>>> first matching constructor and method.
>>>
>>> Pros:
>>>   - simpler, more readable and more reusable code.
>>>   - local adaptations are easy to hande, and reusable for others
>>>   - the slight overhead of using blessed objects and inheritance is
>>> easily gained by the fact that any
>>> operation will only need fetching Koha objects once
>>> (item,library,patron etc) instead of refetching
>>> them numerous times spread across methods calls and loops
>>>   - way less db calls if done right, faster Koha
>>>   - no more C4::Context, hopefully
>>>   - systempreferences can be dramatically reduced, since most of them
>>> are about overrides anyways
>>>   - can be done incrementally, replacing one functionality at a time
>>>
>>> cons:
>>>   - refactoring doesnt make end users happy (but needs to be done in any
>>> case)
>>>   - a bit of work to keep templates happy
>>>   - requires a basic understanding of oop
>>>
>>> So to sum up: We already have a working example for circulation (though
>>> not in production)
>>> that we can demonstrate. It reimplements basically the entire
>>> C4::Circulation, just some small
>>> parts missing. So it can be done.
>>>
>>> But we'd love to hear second opinions from the community! We 

Re: [Koha-devel] new user presentation

[Brendan Gallagher]

Welcome ck!  Great to have you.  Are you in the #koha irc channel yet?
That is a great place to find many people who are very active in Koha.  My
nickname is "bag" - give me a shoutout when you're there and I'll say hi
for sure.

Cheers,
Brendan

On Wed, Mar 28, 2018 at 8:37 AM, c...@interleaf.ie  wrote:

> Hello
>
> My name is Carl, I'm a new member on this list.
>
> I have recently started working as a Developer for Interleaf - a
> company in Ireland providing services for libraries ( https://www.inter
> leaf.ie/ ).
>
> We want to give back to the Koha community, so I will be spending time
> on this mailing list and in Bugzilla, trying to do just that.
>
> I'm rather new to Koha, and will hang around in the background for a
> while to pick up on how things work around here. I've worked as a
> developer and with Linux & BSD systems for a few decades, and will take
> the time to ensure I respect your well documented guidelines.
>
> Cheers
> ck
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Office: Portland, OR - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Koha and Elastic Search used in production ?

[Brendan Gallagher]

Our plan is that Nick is working on getting ES as stable as possible.  He
has invested many days in the past months and will continue to have
different days to work on ES in the coming months.  There are a number of
ES bugs out there that needs testing and sign off.

Our goal is that by 18.05 this will be a viable option for use in
production.  If you have further questions please don't hesitate to ask
Nick.

-Brendan



On Wed, Dec 13, 2017 at 5:56 AM, Paul Poulain 
wrote:

> Hello all,
>
> Is there someone using Koha with ES in production ?
>
> bywater, PTFS-E, Catalyst-NZ, Theke, or any other support company, what's
> your plan ?
>
> BibLibre is planning to invest some effort to work on Koha-ES with UNIMARC
> in the next months, if there are things to share, we would be more than
> happy !
>
> --
> Paul Poulain, Associé-gérant / co-owner
> BibLibre, Services en logiciels libres pour les bibliothèques
> BibLibre, Open Source software and services for libraries
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Office: Portland, OR - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] no acces to debian.koha-community.org

[Brendan Gallagher]

Looks like it’s back up

On Fri, Dec 1, 2017 at 12:19 PM Barton Chittenden <
bar...@bywatersolutions.com> wrote:

> Can confirm. Still down.
>
> On Fri, Dec 1, 2017 at 1:22 PM, Joy Nelson 
> wrote:
>
>> Galen,
>> Are you also working on the wiki.koha-community.org site?  This is still
>> down.
>>
>> -Joy
>>
>> On Fri, Dec 1, 2017 at 8:43 AM, Galen Charlton > > wrote:
>>
>>> Hi,
>>>
>>> It is now back up.
>>>
>>> Regards,
>>>
>>> Galen
>>>
>>> On Fri, Dec 1, 2017 at 9:37 AM, Galen Charlton
>>>  wrote:
>>> > Hi,
>>> >
>>> > I'm taking a look at this now; the VM appears to have fallen over
>>> after a DOS.
>>> >
>>> > Regards,
>>> >
>>> > Galen
>>> >
>>> > On Fri, Dec 1, 2017 at 9:36 AM, Laurent Ducos
>>> >  wrote:
>>> >> always closed, Port 80 seems closed
>>> >>
>>> >> telnet debian.koha-community.org 80
>>> >> Trying 67.220.127.145...
>>> >> 
>>> >> timeout
>>> >> Laurent Ducos
>>> >> Administrateur Systèmes et Réseaux
>>> >> 0974770716
>>> >> 1 décembre 2017 15:28 "Michael Kuhn"  a écrit:
>>> >>> Hi
>>> >>>
>>> > Since about 1 hour I do not have access to
>>> debian.koha-community.org from our public ip
>>> > 91.121.55.79
>>> > Can you give us access again please?
>>> > since others ip everything is ok
>>> >>>
>>> >>> Right now, http://debian.koha-community.org can be accessed again.
>>> >>>
>>> >>> Best wishes: Michael
>>> >>> --
>>> >>> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg.
>>> Fachausweis
>>> >>> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
>>> >>> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
>>> >>> ___
>>> >>> Koha-devel mailing list
>>> >>> Koha-devel@lists.koha-community.org
>>> >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>>> >>> website : http://www.koha-community.org
>>> >>> git : http://git.koha-community.org
>>> >>> bugs : http://bugs.koha-community.org
>>> >> ___
>>> >> Koha-devel mailing list
>>> >> Koha-devel@lists.koha-community.org
>>> >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>>> >> website : http://www.koha-community.org/
>>> >> git : http://git.koha-community.org/
>>> >> bugs : http://bugs.koha-community.org/
>>> >
>>> >
>>> >
>>> > --
>>> > Galen Charlton
>>> > Infrastructure and Added Services Manager
>>> > Equinox Open Library Initiative
>>> > phone:  1-877-OPEN-ILS (673-6457)
>>> > email:  g...@equinoxinitiative.org
>>> > web:  https://equinoxInitiative.org
>>> > direct: +1 770-709-5581 <(770)%20709-5581>
>>> > cell:   +1 404-984-4366 <(404)%20984-4366>
>>>
>>>
>>>
>>> --
>>> Galen Charlton
>>> Infrastructure and Added Services Manager
>>> Equinox Open Library Initiative
>>> phone:  1-877-OPEN-ILS (673-6457)
>>> email:  g...@equinoxinitiative.org
>>> web:  https://equinoxInitiative.org
>>> direct: +1 770-709-5581 <(770)%20709-5581>
>>> cell:   +1 404-984-4366 <(404)%20984-4366>
>>> ___
>>> Koha-devel mailing list
>>> Koha-devel@lists.koha-community.org
>>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>>> website : http://www.koha-community.org/
>>> git : http://git.koha-community.org/
>>> bugs : http://bugs.koha-community.org/
>>>
>>
>>
>>
>> --
>> Joy Nelson
>> Vice President, Director of Implementations
>>
>> ByWater Solutions 
>> Support and Consulting for Open Source Software
>> Office: Fort Worth, TX
>> Phone/Fax (888)900-8944
>> What is Koha? 
>>
>>
>> ___
>> Koha-devel mailing list
>> Koha-devel@lists.koha-community.org
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>>
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/

-- 
Sent from Gmail Mobile
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Next hackfest in Marseille (March 2018)

[Brendan Gallagher]

Moving it closer to the summer may prevent people from attending KohaCon.

On Thu, Nov 23, 2017 at 1:55 AM Magnus Enger  wrote:

> On 16 November 2017 at 15:16, Paul Poulain 
> wrote:
> > Hello,
> >
> > It's time for me to decide when the next hackfest in Marseille will
> happen.
> >
> > Save this date: March 12th-16th. Hoping to see you here !
> >
> > PS: BibLibre turned 10 last month. We will probably do something special
> > during this hackfest (but haven't decided what yet)
>
> Happy anniversary, BibLibre!
>
> I will - sadly - miss the hackfest in Marseille, it is the same week
> as our big, national library conference here in Norway.
>
> Is there any chance you could consider moving the hackfest a month or
> two closer to summer? In the beginning the focus of the hackfest was
> very much signing off and fixing things for the coming release, but it
> has grown to be more like a developer conference, I think, and so the
> timing with the upcoming release might be less important these days?
>
> Just my NOK 0.02. :-)
>
> Au revoir!
> Magnus
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-- 
Sent from Gmail Mobile
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] KohaCon18 - Portland Oregon USA - "Together Towards Tomorrow"

[Brendan Gallagher]

Hello All -

It has been decided that the next KohaCon will be in Portland, OR USA from
September 10th (Monday) to September 12th (Wednesday) in 2018 - followed by
a local cultural day and a 3 day hackfest over the weekend.

The theme for KohaCon18 will be "Together Towards Tomorrow".   A majority
of the focus will be on community building, community engagement, and
building Koha for the future.

We've started planning and starting at the beginning of next year you
should plan on seeing a bunch of information and marketing about the
conference (website, etc.).

We are extremely excited to be hosting and this conference will be tons of
fun!  If you have a chance to mark your calendars please do!

Koha is awesome!

(Much more to follow)

Cheers,
Brendan

-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Office: Portland, OR - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Koha 17.05.00 released!

[Brendan Gallagher]

YAY!  I love releases!  Great job Kyle!

On Wed, May 31, 2017 at 6:09 AM, Tomas Cohen Arazi 
wrote:

> That's awesome! Thanks!
>
> El mar., 30 may. 2017 a las 23:13, Kyle Hall ()
> escribió:
>
>> Hello all!
>>
>> It is my honor to announce the release of Koha 17.05.00!
>>
>> Thanks you to everyone who contributed time and effort making this the
>> best version of Koha yet!
>>
>> The release notes can be found on the Koha Community website:
>> https://koha-community.org/koha-17-05-released/
>>
>> Kyle
>>
>> http://www.kylehall.info
>> ByWater Solutions ( http://bywatersolutions.com )
>> Meadville Public Library ( http://www.meadvillelibrary.org )
>> Crawford County Federated Library System ( http://www.ccfls.org )
>> ___
>> Koha-devel mailing list
>> Koha-devel@lists.koha-community.org
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>
> --
> Tomás Cohen Arazi
> Theke Solutions (https://theke.io )
> ✆ +54 9351 3513384 <+54%209%20351%20351-3384>
> GPG: B2F3C15F
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Office: Portland, OR - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Hackfest in Marseille, book your flight !

[Brendan Gallagher]

Excellent!  We have five people attending from ByWater (Me, Joy, Nick,
JesseM and Michael).  We are hoping to dedicate a full day to RDF (linked
data) work - maybe more!  I am hoping to see as many of you as we can
there.  We always look forward to this hackfest - such a great experience
if you can afford to attend.

Cheers,
Brendan



On Tue, Feb 14, 2017 at 9:25 AM, Paul Poulain 
wrote:

> Hi,
>
> A reminder : the Hackfest in Marseille will take place next month, march
> 20 - 24.
>
> Book your flights & drop me an email (I'm hoping to officially open
> registrations this week)
>
> See you next month !
>
> --
> Paul Poulain, Associé-gérant / co-owner
> BibLibre, Services en logiciels libres pour les bibliothèques
> BibLibre, Open Source software and services for libraries
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Office: Portland, OR - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Git Server

[Brendan Gallagher]

Back up!


On Mon, Oct 17, 2016 at 9:56 AM, Brendan Gallagher <
i...@bywatersolutions.com> wrote:

> Hello All -
>
> Our hosting provider has alerted us to a problem on the host for
> git.koha-community.org.  We are in the process of working with them to
> restore the server.  We will let you all know when it has been restored.
>
> Thanks,
> Brendan
>
> --
> 
> ---
> Brendan A. Gallagher
> ByWater Solutions
> CEO
>
>


-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Office: Portland, OR - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Git Server

[Brendan Gallagher]

Hello All -

Our hosting provider has alerted us to a problem on the host for
git.koha-community.org.  We are in the process of working with them to
restore the server.  We will let you all know when it has been restored.

Thanks,
Brendan

-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] [NEW] What's on in Koha devel

[Brendan Gallagher]

Very lovely report.  I love seeing this and encourage you to continue.  If
others have areas they too are working on - it wouldn't hurt to have good
communication.

thanks,
Brendan

On Wed, Jun 8, 2016 at 7:10 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hi devs,
>
> First, sorry for the [NEW] flag, but it is to make sure everybody
> reading the ML will click :)
>
> I'd like to start a monthly "what's on" email which I will send to
> koha-devel.
> It comes after some discussions at the KohaCon16 with fellows that do
> not have the time to follow what's going on in the community and where
> they could help on important things.
> I used to send one to my partners every month to explain what I did
> and what I plan to do, but actually it sounds more a community report
> to send to the Koha developers.
> So here it is :)
>
> The goal is to resume in a (relatively) short email what has been
> developed in the previous month(s) and what testers/developers can
> focus on. It could be critical/major bugfixes, code
> refactoring/improvements or even big-but-amazing features waiting for
> signoff/QA.
>
> Over the last months I have mainly focused on refactoring stuffs, fix
> plack-related bugs and improvement issues, as well as my usual QA
> work.
> The refactoring part is not going very well, I have suspended it 2
> months ago. The main problem is that the patches are no pushed as fast
> as I expected implying a lot of rebases which is time consuming.
> By refactoring I mean "moving code from old C4 modules to the new Koha
> namespace". The pattern I usually use in the bug report description is
> "Move the stuff related code to Koha::Stuff[s]"
>
> The plack-related bugs were minor, but to provide a full plack
> compatibility it was great to have them push quickly. Luckily they
> have been signed off and QAed quite quickly, only 2 are still waiting
> for QA. The pattern I used in the bug description was "This module is
> not plack safe".
>
> A few words about the performances: You have to know that since 16.05
> (and maybe also 3.22) it's highly recommended to use Plack and
> Memcache to provide your user a good response time.
> We have profiled the code in several areas to find useless processing
> time. In some places, the code has been improved, in others it has
> completely been removed.
> Fixing plack bugs, we have found that we needed to improve our cache
> mechanism and we have introduced a L1 memory cache which should bring
> us performance gain between 3.22 and 16.05. Note that we do not have
> completely finished the work and some more has to been done, so stay
> tuned :) If you have any suggestions or leads on that, please open a
> bug report and assign it to me.
>
> There are 2 critical bugs waiting for signoff (bug 16554 and bug
> 16573), they fix the support of Ubuntu 16.04. So if you plan to
> install Koha on the latest Ubuntu, you should have a look at these 2
> reports.
>
> A major enhancement is in the integration queue and it would be great
> to see some people (librarians would be awesome) involved in the
> testing process. It will allow a patron to place several holds on the
> same record (bug 14695). This feature has been expected for more than
> 3 years now and this is the third attempt.
>
> During the KohaCon16, I have organised a quick brainstorming about our
> implementation of Koha::Object[s] and how we use DBIx::Class. The goal
> was not to find a solution but to present the different issues we
> face. I'd like to bring again this discussion on koha-devel this
> month, listing the pros and cons of our current implementation, and
> gathering ideas to improve it.
>
> Hope this will be helpful for people not heavily involved on IRC or
> the bug tracker.
>
> Cheers,
> Jonathan
>
> References:
> Refactoring to Signoff
>   Bug 15758 - Move the C4::Branch related code to Koha::Libraries - part 4
>   Bug 15803 - Koha::AuthorisedValues - Remove GetAuthorisedValueCategories
>
> Refactoring to QA
>   Bug 15451 - Move the CSV related code to Koha::CsvProfile[s]
>   Bug 15839 - Move the reviews related code to Koha::Reviews
>   Bug 15801 - Move the framework related code to
> Koha::BiblioFramework[s] - part 2
>   Bug 15407 - Move the patron categories related code to
> Koha::Patron::Categories - part 2
>
> Plack bugfixes to QA
>   Bug 16441 - C4::Letters::getletter is not plack safe
>   Bug 16443 - C4::Members::Statistics is not plack safe
>
> Performances entry points are (look at the related bugs using the show
> dependency graph):
>   Bug 15342 - Performance 3.22 - Omnibus
>   Bug 16044 - Define a L1 cache for all objects set in cache
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 

[Koha-devel] 16.05.00-beta tagged

[Brendan Gallagher]

Hi All -

I have tagged a beta release of 16.05.  (I did not include the release
notes yet - I have run them and they look pretty clean - so yay!).  I have
also generated a tarball but I need access to the downloads - I am in the
process of getting that worked out).

The plan is that on Friday - I'll roll a RC1.

I will be releasing on May 26th.

(If you see something that I have missed - please don't hesitate to talk to
me)

Thanks,
Brendan

-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Update on RM

[Brendan Gallagher]

Hi All -

I had a really busy week last week and was not able to dedicate time
towards testing and pushing code.  I have a busy Monday morning, but then
after that I will get that PQA low again.  We have about 2 weeks until the
freeze, just a reminder, not a rallying call yet.  Hoping the final month
after the freeze we can get Master wicked stable.  :).

Cheers,
Brendan


-- 
Sent from Gmail Mobile
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Final stretch before the next release (3.24 | 16.05)

[Brendan Gallagher]

On Mon, Apr 11, 2016 at 3:50 AM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hi devs,
>
> The next Koha release will arrive soon and the feature freeze is
> coming in 2 weeks!
> I'd like to mention some works we really should have in this release:
>
> 1/ Speed improvements
> * Koha::Cache
> Interesting ideas have been implemented recently, but only few have been
> pushed.
> We can expect a real gain of performances, our cache system
> (Koha::Cache) has been improved with bug 11998 and 16044 but is not
> perfect yet. To make it great, we absolutely need patches from 16221
> (Use Storable::dclone() instead of Clone::clone() for L1 cache
> deep-copying mode), and then 16140 (Only clear L1 cache when needed)
> and 16166 (Improve L1 cache performance).
> Bug 16105 (Cache::Memory is loaded even if memcache is used) is also
> cache-related.
>
> * Search
> There are 3 bug reports blocking bug 15262 (Run Koha Run. Koha search
> should be fast again) : bug 15263 (XSLT display fetches sysprefs for
> every result processed) is waiting for QA but 16041 is waiting for
> signoff. Note that I have opened 16167 to discuss about the possible
> removal of authorised value images. If you know someone using them,
> please add a comment on the bug report.
>
> To have an overview of what has been done around the performance
> optimisation during the last months or still need to be done, have a
> look at the bug 15342 (Performance 3.22 - Omnibus).
>

Very important stuff here.  This should be priority for everyone.


>
> 2/ Elastic Search
> A testing day is organised soon (today and tomorrow), stay tuned!
>
> 3/ Rewrite/refactoring
> I have worked a lot on refactoring some parts of Koha the last months.
> There are 5 left waiting for love:
> Bug 15801 - Move the framework related code to Koha::BiblioFramework[s] -
> part 2
> Bug 15758 - Move the C4::Branch related code to Koha::Libraries - part 4
> Bug 15407 - Move the patron categories related code to
> Koha::Patron::Categories - part 2
> Bug 15498 - Replace ExportWithCsvProfile with ExportCircHistory
> Bug 15451 - Move the CSV related code to Koha::CsvProfile[s]
>
> I really would like to see them included into the next release.
> For the first 3, it's the continuation of parts already pushed, it
> would make sense to have them too.
>
> 4/ jQuery upgrade
> Owen suggested to upgrade our jQuery on bug 15883, it is a nice to
> have for the next release.
>
> 5/ Bug fixes
> * CGI->multi_param
> You have certainly notice the "CGI::param called in list context"
> warnings in the logs. We are going to get rid of them with bug 16154 -
> Replace CGI->param with CGI->multi_param in list context
> * Regression on currency
> This will become a blocker if not signed off soon. See bug 16227 - The
> currencies of vendor and order do not display correctly
> * The OPAC is not accessible if JS is disabled (blocker)!
> See bug 16210 (Bug 15111 breaks the OPAC if JavaScript is disabled) for a
> fix
>
> 6/ Versioning change
> It seems that we voted [1] for changing the versioning to be date
> based. Does someone work on that? There are adjustments to do to the
> codebase to make it work. But we also need to decide how to number the
> 2 annual major versions and the minors.
>

I was thinking 2 majors would be 16.05 and 16.11
minors would be 16.05.01 (for first RMaint of 16.05) and increase
incrementally.
Dev (unstable) would be 16.06 and then 17.00

I am and was willing to work on the patches for the version changes but was
waiting until after the Freeze to do that.  If you have any comments for me
Jonathan that's great - I'll always take them.


>
> Feel free to add more if you think about something.
>
> Note: please sort by severity when you are searching for a bug to sign
> off [2], blocker, critical and major have to be signoff before
> cosmetic bugs ;)
>
> Cheers,
> Jonathan
>
> PS: Note that there are 5 points before the 6th!
>
> [1]
> http://meetings.koha-community.org/2016/genereal_irc_meeting_9_march_2016.2016-03-09-20.00.log.html
> )
> [2]
> https://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=Needs%20Signoff=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cbug_severity_id=160792=bug_severity%2Cassigned_to%2Cbug_id%20DESC_based_on=Needs%20Signoff_format=advanced
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] International ES sign-off testing day (next Tuesday/Wednesday)

[Brendan Gallagher]

Hi -

Well I didn't want to put times in there exactly - I was sort of hoping for
a day of work.  So that being Wednesday for the New Zealand types and
Tuesday for the rest of us.  Nick (kidclamp) will have two identical
servers up (one ES and one Zebra) by the end of the day (today - Monday for
him).  So anyone and everyone will be able to test.  Ideally Chris will be
ready for patches or answering questions on his Wednesday morning (9am New
Zealand time).

HTH
Cheers,
Brendan

On Sun, Apr 10, 2016 at 2:58 AM, Katrin Fischer <katrin.fischer...@web.de>
wrote:

> Hi Brendan,
>
> could you share some link as we have on the agendas for the meetings to
> define the time window?
>
> Have a nice weekend,
>
> Katrin
>
> Am 07.04.2016 um 23:52 schrieb Brendan Gallagher:
> > Hello All -
> >
> > I am hoping that we could have a day next week where we are in irc
> > channel #koha and do some testing of Elastic.  Ideally target that to be
> > Wednesday for NZ UTC +12 (iirc) and Tuesday morning for me.  The idea is
> > that we'll have Chris (rangi) in channel to look at problems and fix
> > problems that day as we bring them up to him.  Nick (kidclamp) from
> > ByWater will also be present as he has done the most testing on our side.
> >
> > Ideally we'll have some ES installs setup - hopefully (we bywater will
> > have 2 identical datasets - 1 running ES and 1 running zebra (but with
> > the ES code installed))...  More setups are welcome.
> >
> > We could hopefully get everything set well so that we could get a
> > sign-off that day and get this into QA.  Also another thought is that we
> > edit a wiki-page so that we can list things that ES is doing already -
> > what system preferences effect it etc.
> >
> > Thanks,
> > Brendan
> >
> > --
> >
> ---
> > Brendan A. Gallagher
> > ByWater Solutions
> > CEO
> >
> >
> >
> >
> > ___
> > Koha-devel mailing list
> > Koha-devel@lists.koha-community.org
> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> > website : http://www.koha-community.org/
> > git : http://git.koha-community.org/
> > bugs : http://bugs.koha-community.org/
> >
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] International ES sign-off testing day (next Tuesday/Wednesday)

[Brendan Gallagher]

Hello All -

I am hoping that we could have a day next week where we are in irc channel
#koha and do some testing of Elastic.  Ideally target that to be Wednesday
for NZ UTC +12 (iirc) and Tuesday morning for me.  The idea is that we'll
have Chris (rangi) in channel to look at problems and fix problems that day
as we bring them up to him.  Nick (kidclamp) from ByWater will also be
present as he has done the most testing on our side.

Ideally we'll have some ES installs setup - hopefully (we bywater will have
2 identical datasets - 1 running ES and 1 running zebra (but with the ES
code installed))...  More setups are welcome.

We could hopefully get everything set well so that we could get a sign-off
that day and get this into QA.  Also another thought is that we edit a
wiki-page so that we can list things that ES is doing already - what system
preferences effect it etc.

Thanks,
Brendan

-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Freeze/Release dates coming up for 16.05

[Brendan Gallagher]

Hi All -

I will be setting a feature freeze of April 28th (End of Day) and a release
date of May 26, 2016.  All those patches that are not PQA by the end of day
28th April will not have a chance to be in the 16.05 release.

Thanks,
Brendan
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] 22nd March - Dev meeting in IRC at 19 UTC

[Brendan Gallagher]

https://wiki.koha-community.org/wiki/Development_IRC_meeting_22_March

Please see the agenda for action and discussion items.

   - 22 March 2016, 19 UTC Time and Date.com converter for various local
   times
   




Thanks Brendan.
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Packing needs - status to add to bugzilla and the dashboard?

[Brendan Gallagher]

Cool - I added some quick notes to the RM spot - I'd be interested in
seeing others fluff that out.

On Tue, Mar 8, 2016 at 3:03 PM, Galen Charlton <g...@esilibrary.com> wrote:

> Hi,
>
> On Tue, Mar 8, 2016 at 12:50 PM, Brendan Gallagher <
> i...@bywatersolutions.com> wrote:
>
>> Do we have a defined role description of responsibility of the Packaging
>> Manager?  (I've only read Robin's posts to the mailing list before - is
>> that it?)
>>
>
> We do now, seeded with my view of the position:
>
> https://wiki.koha-community.org/wiki/Project_roles#Packaging_manager
>
> On a side note, the overall page is new; I'm figuring that it might be a
> useful exercise to outline minimum role responsibilities for all of the
> named project positions.
>
> 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
>



-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Fwd: Packing needs - status to add to bugzilla and the dashboard?

[Brendan Gallagher]

Thanks Liz.

-- Forwarded message --
From: Liz Rea <l...@catalyst.net.nz>
Date: Tue, Mar 8, 2016 at 12:37 PM
Subject: Re: [Koha-devel] Packing needs - status to add to bugzilla and the
dashboard?
To: Brendan Gallagher <i...@bywatersolutions.com>


Robin wrote a couple of quite good wiki pages on this subject:

https://wiki.koha-community.org/wiki/Building_Debian_Dependencies
https://wiki.koha-community.org/wiki/Building_Debian_Dependencies/Dependency_Guidelines




On 09/03/16 06:50, Brendan Gallagher wrote:

Yup all good points.  Not to put it all on the PM - but I think a way to
track this in BZ is needed.  A better workflow - perhaps based on Chris's
point - a "failed QA - needs package" status (or some worded status)?

Do we have a defined role description of responsibility of the Packaging
Manager?  (I've only read Robin's posts to the mailing list before - is
that it?)


On Tue, Mar 8, 2016 at 9:37 AM, Galen Charlton <g...@esilibrary.com>
<g...@esilibrary.com> wrote:


Hi,

On Tue, Mar 8, 2016 at 12:30 PM, Chris Cormack
<chr...@catalyst.net.nz> <chr...@catalyst.net.nz>
wrote:

I don't think it's fair to push this all on the package manager. If a dev


introduces new dependencies that need packaging, it should be their

responsibility to make sure this is done.


Indeed. I am willing to build *some* packages (and submit them to Debian),
but that willingness is decidedly not infinite.

The first question that somebody who proposes to add a new dependency
should ask themselves is this: is there a way to accomplish the task at
hand without adding a new dependency?  If not, can the task at hand be
accomplished using packages that are already in Debian stable?  If not,
does the dependency at least have an active third-party ITP (intent to
package) in the Debian bug tracker?

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



___
Koha-devel mailing
listkoha-de...@lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/


-- 
--
Liz Rea
Catalyst.Net Limited
Level 6, Catalyst House,
150 Willis Street, Wellington.
P.O Box 11053, Manners Street,
Wellington 6142

GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com


signature.asc
Description: PGP signature
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Packing needs - status to add to bugzilla and the dashboard?

[Brendan Gallagher]

Hello All -

I'd like to have a chance to talk about the packing work flow at the next
developers meeting or even the general meeting.

My thoughts are that we need a status in Bugzilla that says something like
"Needs package created" or something.  Also add a little spot on the
dashboard under the Bugs Statuses which has a canned search for that queue.

I imagine the workflow being something like...

1. RM pushes code to master
2. RM changes status to "needs package created"
3. PackingManager creates package
4. PM changes the status to "Pushed to Master"

The work flow is important and I'd like to make it as transparent as
possible and make sure that we don't miss something.  Robin, Galen, or
others do you have any thoughts on this?

Thanks,
Brendan

-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] RM update - May 2nd

[Brendan Gallagher]

Hi All -

It's been a little bit of time since I've posted.  Sorry it's ended up
being a long email.   ( Easier to say most of this here instead of posting
all this into an IRC meeting) ;)

Currently the PQA is very low.  I encourage all of you to review the needs
sign-off page and test some of the wonderful code that many of us have
written.  Just to remind - the dashboard is a great place to start
(everyone should have that one bookmarked - I hope I didn't date myself
with that term).  http://dashboard.koha-community.org/   -  Also here is a
link to the Bugzilla page that has the Needs Signoff queue -
http://tinyurl.com/h3zdxec .  Remember that Bugzilla is only the name of
the tracker that we are using - it's not only bugs but also features and
other coding needs for Koha.  ;)   Also a reminder for those that are newer
to testing - try out the sandboxes -
https://wiki.koha-community.org/wiki/Sandboxes (please remember that you
can also ask any of us for help).

I know that there are a few things that I need to follow up on for some
recent patches that have been pushed.   I'm on them and tracking them.
Thankfully no one is using Master in production :)  As always if I have
missed something or I have made a mistake - please let me know and I thank
you all for the times you have pointed out a spot I missed (those curly
brackets if you know what I mean)

Somethings I'd like to concentrate on going forward.

1. Speed.  two bugs in general -
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15350
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15341
Any and all help is welcome here.  Jonathan has been presenting thoughts
and comments about this for awhile now - let's all help there. There are
some others too and we should all think about this.  I feel like we are
loading too much with each page.  Also dbix::class should be examined.

2. Elastic Search -
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478  Is the
main bug where there are comments, code and thoughts.  I think we need a
sign-off on this and get this into QA with larger discussions happening.
The Main goal for now is that it doesn't break anything with Zebra and we
can push this in experimental.  There are some good comments and questions
on the bug.

3. Staying on top of PQA queue so our developers do not have to spend time
rebasing code.  I will hopefully maintain that.  (sorry for those that have
had to rebase so far)

4. Continue to encourage new signoff champions!  This is on all of us to
encourage and help those that want to do this and have time to do it.  We
can do it.

5. EDIfact code - needs a signoff.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7736  and
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15630  great work
by PTFS-europe and nice job by Kyle Hall on making it plugable so that it
works around the standards.  (Also I encourage PTFS-europe on submitting
more of their code - they are sitting on a few gems right now that will be
great for Koha - so if you see their code come it - let's test it).

6. Jenkins - I would like to see Jenkins pass as stable for Master in the
near future.  I will be spending sometime working on that.

I know this turned into a long email.  But let's do it!

Cheers,
Brendan







-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Huge performance issue cause by bug 13618 (XSS)

[Brendan Gallagher]

I have been slow to push anything much since I pushed that big one to give
a little time.  I can revert that patch set which is still an option

On Wednesday, February 10, 2016, Marcel de Rooy 
wrote:

> Too bad, especially since we already have performance issues..
> I would go for option 1 part a = revert. (It is one of the last pushes, I
> think.)
> And some further research on 2,3 or 4 ? :)
>
> 
> Van: koha-devel-boun...@lists.koha-community.org  [
> koha-devel-boun...@lists.koha-community.org ] namens
> Jonathan Druart [jonathan.dru...@bugs.koha-community.org ]
> Verzonden: woensdag 10 februari 2016 15:49
> Aan: koha-devel@lists.koha-community.org 
> Onderwerp: [Koha-devel] Huge performance issue cause by bug 13618 (XSS)
>
> Hi devs,
>
> I have a very bad news...
> Working on bug 15715, I have found that the patchset introduced by bug
> 13618 (Prevent XSS in the Staff Client and the OPAC) causes a very
> important performance issue.
>
> Indeed, for each variable displayed in the template, a
> Template::Stash::AutoEscaping->get method is called.
>
> To try and understand the problem, I have put the following snippet in
> the mainpage.pl script:
> +my @loop;
> +for my $i ( 0 .. 1 ) {
> +push @loop, {
> +foo => 'my foo',
> +bar => 'my bar',
> +};
> +}
> +$template->param( loop => \@loop );
>
> and then, in the template
> +[% FOR l IN loop %]
> +[% l.foo %] [% l.bar %]
> +
> +[% END %]
>
> It will display 10k foo and 10k bar
> There are indeed 20k (+ delta) calls to the
> Template::Stash::AutoEscaping method, as expected.
> But the load of the page increases from 2sec to 10sec (no plack,
> measured with Firebug > network tab)
>
> On catalogue/search.pl, 1800 calls, from 6sec to 6.5s
>
> On authorities/
> authorities.pl?breedingid=186=CORPO_NAME=0
> (From bug 15715), 64k calls (!!!) from ~10sec to ~4min
>
> On cataloguing/addbiblio.pl?biblionumber=1, 13k calls, from 3sec to 9sec
>
> Do not take these measures too strictly, but they give an idea of the
> issue...
>
> So I don't see a lot of methods to fix that:
> 1/ Revert and abandon 13618
> 2/ Understand how it's possible to have 60k calls to display a form
> and try to improve these areas
> 3/ Profile Template::Stash::AutoEscaping to know if we cannot optimise
> what it does
> 4/ Any brilliant ideas?
>
> Jonathan
>
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15715
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13618
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org 
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org 
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>


-- 
Sent from Gmail Mobile
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] It's that time - Calling for a dev meeting in IRC - Feb 2nd

[Brendan Gallagher]

Hello All -

I'd like to call for a dev meeting(QA meetup/catch up) for Feb 2nd at
15utc.  The reason there is such short notice was that I thought we should
complete the meeting so we can bring any announcements to the General IRC
meeting the following day.

Please see the agenda.
https://wiki.koha-community.org/wiki/Development_IRC_meeting_2_February_2016

Time converter -
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meeting=20160102T15


Thanks much,
B

-- 
---
Brendan A. Gallagher
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Hide records on Leader 05 = d in OPAC

[Brendan Gallagher]

Sounds good to me David.  If you get some code up there I'll find someone
to Test.

Cheers,
Brendan

On Sunday, January 10, 2016, David Cook  wrote:

> Hi all:
>
>
>
> Recently, http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11084
> was pushed to master. It adds a cronjob which deletes bibliographic
> records, if their LDR05 is “d” (ie status deleted).
>
>
>
> While I’m all for that, I’m thinking that it would also be a good idea to
> hide these records with LDR05 “d” in the OPAC before the cronjob is run.
>
>
>
> We can’t necessarily rely on all Koha instances running this cronjob, nor
> can we rely on the frequency. Shouldn’t we be hiding these records from the
> OPAC as soon as they’re marked as “deleted”?
>
>
>
> I’ve opened a bug for this purpose:
> http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15537
>
>
>
> It should be a pretty easy change, especially when using special attribute
> @attr 14=1 to avoid past OpacSuppression problems, but I thought I’d ask
> folk if it’s something they’d be interested in. We’d probably still want to
> see these records in the Staff Client, as we want to be able to find all
> records in the database in the Staff Client.
>
>
>
> I admit that I have a special interest in this where I might be overlaying
> existing records using a mostly empty skeleton record generated from an
> OAI-PMH identifier and a OAI-PMH deleted status (OAI-PMH doesn’t send
> metadata for deleted records). I’d match the existing record in Koha using
> the identifier, and then set LDR05 to “d” in accordance with the OAI-PMH
> deleted status. Then, that record would disappear from the OPAC, so that
> end users don’t see this skeleton record.
>
>
>
> David Cook
>
> Systems Librarian
>
> Prosentient Systems
>
> 72/330 Wattle St, Ultimo, NSW 2007
>
>
>


-- 
Sent from Gmail Mobile
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Next General IRC meeting

[Brendan Gallagher]

Hello All -

The next meeting is 13 January 2016 at 20:00 UTC

Conversion to your local time: Time and Date.com converter for various
local times
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+Meeting=20160113T20>


Here is the agenda -
http://wiki.koha-community.org/wiki/General_IRC_meeting_13_January_2016

Thanks and I hope to see a lot of you there.  One thing we need to do is to
encourage more people to sign-off on bugs.  I think I will add a
brainstorming session to agenda for people to throw out ideas for
encouragement for sign-offs (also see Jonathan's email for more sign-offs).

Cheers,
Brendan Gallagher
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Start of new release. Some updates.

[Brendan Gallagher]

Now that the release is out, I wanted to give a quick little update for the
following release.

I will be traveling out of the country from December 1st till December
10th.

Really what my plan is that the first few weeks we will not really be
pushing new features.  We want to concentrate on any bugs that are needed
for 3.22.x and master.  Kyle will be in the office and handling those
needs.  He will push and work on those bugs for us.

Once I am back and settled in I will concentrate on bugs and new features.

I am very open for discussion and I would like to talk with as many of you
as I can about the great work that you're doing.  Perhaps I will get a
chance to speak with each of you about your plans development wise the next
few months - so we can have a clear path on timing, getting you help
testing your developments, and of course working with the whole team to
help QA code.  I think as long as we keep our expectations on the same
page, we'll have a lot of success helping you meet the goals of a great
stable release.

Anything that we can do to help promote more initial sign-offs (probably
our biggest bottleneck) the better.  Let's see what things we can implement
to encourage more of us testing the code.  I will be encouraging our
partner libraries and our staff to be doing as much as we can even with our
busy schedules.  Be proud!

I plan on doing a weekly release newsletter.

Thanks and as always don't hesitate to ask some questions.


Brendan A. Gallagher
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] INSTALL.debian is outdated

[Brendan Gallagher]

Maybe we just bring this up for a vote at an IRC meeting?

On Thu, Nov 12, 2015 at 4:06 AM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> 2015-11-11 22:37 GMT+00:00 Robin Sheat :
> > Aparrish schreef op wo 11-11-2015 om 08:13 [-0700]:
> >> I followed the official instructions:
> >>
> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debian;hb=HEAD
> >
> > We need to delete those, they're from 2012 and are super out of date.
>
> Shall we 1) delete them, 2)replace them with the content of the wiki
> page or 3) just put a link to the wiki page?
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] October 14th Dev Meeting in IRC (testing needed!)

[Brendan Gallagher]

Hello all -

I just wanted to make sure everyone who didn't attend the meeting have the
notes (please see below).  We have feature slush set for October 26th.
Please we need lots of help testing.  Now is an excellent time for a good
strong solid 2 week sprint on bug testing etc.  There are some big
developments that need testing plus other bugs too.  Any and all help is
great!

Minutes:
http://meetings.koha-community.org/2015/development_irc_meeting_14_october_2015___part_1.2015-10-14-14.08.html

Minutes (text):
http://meetings.koha-community.org/2015/development_irc_meeting_14_october_2015___part_1.2015-10-14-14.08.txt

Log:
http://meetings.koha-community.org/2015/development_irc_meeting_14_october_2015___part_1.2015-10-14-14.08.log.html

Thanks and Cheers,
Brendan

-- 
---
Brendan A. Gallagher
ByWater Solutions
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Hackfest in Marseille 2016

[Brendan Gallagher]

I would vote for Sept/October - Since I haven't been to Marseille any time
besides March.

On Fri, Oct 9, 2015 at 3:40 AM, Paul Poulain 
wrote:

> Hello world,
>
> Next year, the KohaCon will be in Europe, in may/june.
> BibLibre is planning the 2016 hackfest in Marseille. Usually it's in march.
>
> So there will be 2 events in a short duration.
>
> A quick poll, do you think:
>  * we should keep the hackfest in march
>  * it would be better to have the hackfest in sept/oct
>
> (motivate your choice if you think it's worth ;-) )
>
> --
> Paul Poulain, Associé-gérant / co-owner
> BibLibre, Services en logiciels libres pour les bibliothèques
> BibLibre, Open Source software and services for libraries
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Kohadevbox for testing Packages+Plack

[Brendan Gallagher]

Thanks Tomas -

I have started to test this and play around with it.  Are others finding
the time to do that as well?  Great stuff here and really important for all
of us.  Please share your thoughts and comments with us all.

We are getting closer to 3.22 and it looks like we're going to finally be
fast - this plack work is awesome and so important!  (plus we also need
lots of help with Elastic Search, Browse, and RESTful apis - we need to get
that functionality into Koha).  Please now is the time to test, share
comments, and let's do this - we can do it!!!

Cheers,
Brendan

On Fri, Sep 25, 2015 at 2:53 PM, Tomas Cohen Arazi 
wrote:

>
>
> 2015-09-23 6:57 GMT-03:00 Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org>:
>
>> It works perfectly with a Jessie host.
>> Note that I am using vagrant 1.6.5 and ansible 1.7.2.
>>
>> Some questions:
>> 1/ > $ export SYNC_REPO=/home/katrina/kohaclone
>> Why this variable is not in the vars/user.yml file?
>> The process explodes if not defined:
>> TASK: [kohadevbox | Gitify the Koha instance]
>> *
>> failed: [jessie] => {"changed": true, "cmd": "./koha-gitify kohadev
>> /home/vagrant/kohaclone", "delta": "0:00:00.045243", "end":
>> "2015-09-23 09:12:58.035161", "rc": 2, "start": "2015-09-23
>> 09:12:57.989918"}
>> stderr: ERROR: git checkout not found at (/home/vagrant/kohaclone)
>>
>
> I've just fixed it so it clones the community repo (whatever you configure
> in user.yml actually) if the environment variable is not defined.
>
>
>> 2/ Can we imagine several instances running? How can we access them
>> separately?
>>
>
> It is not that easy, because we are mapping the ports at
> Vagrantfile-level. A combination of (host machine) /etc/hosts tweaks and
> apache vhosts tweaks (vagrant machine) might do it.
>
>
>> 3/ Can we imagine a way to automatically insert a specific DB (from
>> the contrib/sandboxes repo for instance)?
>>
>
> That'd be great too. Right now I've just prepared the field for
> skip_webinstaller. Next could be that. Any help is welcome too ;-)
>
> --
> Tomás Cohen Arazi
> Theke Solutions (http://theke.io)
> ✆ +54 9351 3513384
> GPG: B76C 6E7C 2D80 551A C765  E225 0A27 2EA1 B2F3 C15F
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] RESTful Apis

[Brendan Gallagher]

Great, thank you Julian and I see some recent action too!  Let's all
continue to test this!  Very critical for us to have RESTful Apis in the
3.22 release.  I'd also like to point out that the elastic search code
needs more testing and searching done on it.  Please just add the comments
to the bug and we will meet them as they come in.  Also very critical for
this coming release.  Is anyone close to signing off on either of these
large ideas?

Thanks much,
Brendan

On Monday, September 21, 2015, Julian Maurice <julian.maur...@biblibre.com>
wrote:

> It has been decided during the dev meeting to push first a minimal version
> of the API code, which will handle only one type of authentication
> (cookie), and work in CGI mode.
> Then we will start to build the rest on top of that.
> So I cleaned up the bug 13799, which I think is now as simple as it can
> be, and is waiting for signoffs.
>
> However, my last comment (
> http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13799#c147)
> raises a few concerns that need to be addressed first. It's about including
> a patch that uses a Swagger2 feature marked as experimental.
>
>
>
> Le 20/09/2015 02:11, Brendan Gallagher a écrit :
>
>> Hi All -
>>
>> For those of you in the know, can we get a public update of where we are
>> with this?  I believe we had some new action items out of the last IRC
>> dev meeting, and I'm curious as to what we've met so far.  Also there
>> was some discussion/difficulty with perhaps having to run something
>> (mojolicous iirc) as a daemon vs not having to.  (I think maybe Tomas
>> was going to help with the technical difficulty on that.
>>
>> I'm just looking for updates on this whole thing.  We've got some
>> excited thoughts, ideas, and plans to use these APIs asap.
>>
>> Oh yeah BTW Elastic is completely developed and ready.  We need tons of
>> testing etc. and reports to Robin for "tweaking" the code for the
>> results we are looking for.  Please if you have time - test ES and send
>> your feedback.  We've got sometime left for this to be an option for the
>> next release (and the RESTapis too).
>>
>> Thanks much,
>> Brendan Gallagher
>>
>> --
>>
>> ---
>> Brendan A. Gallagher
>> ByWater Solutions
>> CEO
>>
>> Support and Consulting for Open Source Software
>> Installation, Data Migration, Training, Customization, Hosting
>> and Complete Support Packages
>> Headquarters: Santa Barbara, CA - Office: Redding, CT
>> Phone # (888) 900-8944
>> http://bywatersolutions.com
>> i...@bywatersolutions.com <mailto:i...@bywatersolutions.com>
>>
>>
>> ___
>> Koha-devel mailing list
>> Koha-devel@lists.koha-community.org
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>>
>>
>
> --
> Julian Maurice <julian.maur...@biblibre.com>
> BibLibre
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>


-- 
Sent from Gmail Mobile
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] RESTful Apis

[Brendan Gallagher]

Hi All -

For those of you in the know, can we get a public update of where we are
with this?  I believe we had some new action items out of the last IRC dev
meeting, and I'm curious as to what we've met so far.  Also there was some
discussion/difficulty with perhaps having to run something (mojolicous
iirc) as a daemon vs not having to.  (I think maybe Tomas was going to help
with the technical difficulty on that.

I'm just looking for updates on this whole thing.  We've got some excited
thoughts, ideas, and plans to use these APIs asap.

Oh yeah BTW Elastic is completely developed and ready.  We need tons of
testing etc. and reports to Robin for "tweaking" the code for the results
we are looking for.  Please if you have time - test ES and send your
feedback.  We've got sometime left for this to be an option for the next
release (and the RESTapis too).

Thanks much,
Brendan Gallagher

-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] [QA] Too many major and critical bugs in the QA queue

[Brendan Gallagher]

I can look at a few of these starting on Monday afternoon.

-Brendan

On Thu, Aug 27, 2015 at 8:04 AM, Jonathan Druart 
jonathan.dru...@bugs.koha-community.org wrote:

 Hi QAers,
 There are 18 bug reports in the QA queue which are either major or
 critical.
 For most of them I am the author or am not able to QA on it.
 Please have a look at them in priority.

 Here the list with the people out to QA (JD Jonathan Druart, KH Kyle Hall)

 14098 Regression in Marc Modification Templates
 Major (JD, KH) Really, this one should be tested and passed as quick
 as possible, I have already try and draw the attention on this one but
 without success...

 13411 SIP server returns not ok for checking in items that are not checked
 out
 Major (KH) I can try and take this one, but SIP... Colin maybe?

 8723  holds don't transfer when moving items
 Critical (JD) An old Critical, so certainly not *very* critical, but
 maybe a little bit :)

 12525 Patron Lists aren't added to list pulldown when created from Patron
 search
 Major (JD) Open by Kyle, so maybe you could be a good candidate? :)

 13943 Cancelling the deletion process of an item deletes item anyway
 Major (JD) This one is really bad. Are you sure you want to delete?
 No? Ok too bad for you!

 6756  Patron anonymizing tool reports false success
 Major (JD) 140 lines of tests added for a 3 lines patch, that would be
 worthwhile!

 14205 Deleting an Item/Record does not remove link to course reserve
 Major (JD) Maybe not major, but quite easy to tests.

 10005 inventory checks items in without warning
 Major (JD) This one is waiting for a patch for more than 2 years, now
 it has one!

 12965 can create an item type that already exists
 Major (JD) Just to be consistent... Really easy to test.

 12885 Search fails with errors when HTML5 Media is enabled and url has
 plus (+) charcters
 Major (JD) Really easy to test.

 14584 Encoding broken with system preferences
 Major (JD) Encoding problem!

 14598 itemtype is not set on statistics by C4::Circulation::AddReturn
 Major (KH) I have let a comment, but you can have a look too.

 14685 Cannot set guarantor for a child account
 Critical (JD) Yes you have correctly read, it's critical: regression
 in stable branches!

 14155 Placing holds via ILSDI bypass some checks
 Major (JD, potential conflict of interest)

 14597 Reverting a batch where a record overlaid is now deleted record will
 fail
 Major (KH) I have let a comment, Kyle has answered, but needs another
 fresh look.
 Kyle, maybe should we let the Logger decision for another patch (one
 which would not be major)?


 14141 Changing the Library for a notice duplicates the notice instead
 of updating it
 Major (JD) Not a good patch, but a quick workaround.

 14709 The export tool is broken if used from the command line
 Major (JD) Very small patch, all is in the title. Could be a critical
 one, it's in 3.20.x

 14509 Koha still allows spaces at the end, beginning or as your password
 Major (JD) quick follow-up for stable branches.

 I can do all my best to patch major and critical bugs, but if nobody
 tests them, I feel  a bit useless...

 Thanks in advance,

 Jonathan
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Thoughts about timing and Koha schedules

[Brendan Gallagher]

Hi All -

ByWater is on its 7th year, so we have a solid set of data for analyzing,
and recently I've noticed a few things.  Let me try and paint the picture.

Major Koha releases are every six months and usually the 22nd day of the
month, with the target being November and May.  (Please correct me if I am
wrong)

Library funding cycles in the US run either fiscal year (July to June),
Calendar year  (January to December), or some odd fiscal year close to the
July~June year.  Ok that being said from the time management situation with
ByWater that introduces a few complexities.

(Let me describe the workflow and maybe you'll see what I am talking about)
 Most of the time a library will sign a migration contract with us that
dictates we must have them go-live before a certain fiscal date OR the
library isn't really able to sign a contract for services until a certain
fiscally motivated date (which places us into a similar roll-out).  That
being said we find that May and November (plus and minus a month) are our
busiest times of the year.  I've got 3 people on the road for
education/training, 3 people heavily in the fields of migrations scripts,
and 3 developers that are heavily in the field of meeting development
expectations for lots and lots of go-lives (*note - plus additional staff
to support an influx in tickets or other support needs during a go-live
period).

So if we slide the releases to say February and August - I would be able to
dedicate more man power (9+ people from the above paragraph) around the
heavy testing/ debugging / bug writing/squashing periods for a release.  I
know I know - there isn't really a time that Koha doesn't need more
testing, but I've noticed that the volunteer effort is usually much
greater/demanding the closer we are to major release date.

I am wondering if others are finding the same with their work schedules
(other support providers, academic institutions, public institutions, and
my favorite volunteers).  Are there certain times of the years where your
day job is predictably busy that you aren't able to dedicate the resources
that you want towards the greatest project in the world Koha.

With the data set that we're sitting on here, we are constantly seeking
ways that we can contribute more.  Just a thought and was curious if others
analyzed a similar aspect with their environment and perhaps maybe we
should bring such a discussion into the open or a general IRC meeting.
Especially any of us that are support providers we should be always be
thinking about how we can do more for Koha.

Thanks and Cheers (another sleepless night thinking about my favorite
subject - Koha),
Brendan

-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Portland, OR - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Improving Plack intranet performances (circulation module)

[Brendan Gallagher]

Awesome

On Tue, Aug 18, 2015 at 1:11 PM, Tomas Cohen Arazi tomasco...@gmail.com
wrote:

 It is done. The patches to integrate Plack with the packages are ready.

 2015-05-28 12:22 GMT-03:00 Tomas Cohen Arazi tomasco...@gmail.com:

 I resumed my work on automating plack usage on packages installs. News
 about it soon.

 2015-05-28 12:21 GMT-03:00 Fridolin SOMERS fridolin.som...@biblibre.com
 :

 Very good news, thanks

 Le 27/05/2015 12:14, Julian FIOL a écrit :

 Hi everyone,

 Using Devel::NYTProf on a Plack config, I noticed that when we checkout
 an item in the circulation page, there is a really long time spent
 creating the database schema.

 By adding the import of *Koha::Schema* in the *intranet.psgi* file, we
 can see a significant improvement of the time spent loading the
 circulation page.

 Please find here
 
 http://www.slideshare.net/JulianFiol/koha-circulation-checkout-improvement
 
 (in full screen) the proof of what I'm saying.

 I have also added the manipulations to do into the Plack
 http://wiki.koha-community.org/wiki/Plack#Improving_Plack_performance
 wiki.

 Regards,
 Julian FIOL



 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/


 --
 Fridolin SOMERS
 Biblibre - Pôles support et système
 fridolin.som...@biblibre.com
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




 --
 Tomás Cohen Arazi
 Prosecretaría de Informática
 Universidad Nacional de Córdoba
 ✆ +54 351 5353750 ext 13168
 GPG: B76C 6E7C 2D80 551A C765  E225 0A27 2EA1 B2F3 C15F



 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Koha::Object

[Brendan Gallagher]

We are very much interested in this.  Both the great start that Olli is
doing and the excellent ideas that Robin has to add on top.  In Fact we've
added this to our list to find funding for, for after we've finished the ES
project.  So help us finish the ES project faster (hint hint - test test -
more information is coming in the newsletter) and we'll start raising money
towards an excellent Auth (in the future).

Cheers,
Brendan

On Mon, Jul 27, 2015 at 9:30 PM, Robin Sheat ro...@catalyst.net.nz wrote:

 Kivilahti Olli-Antti schreef op di 28-07-2015 om 03:57 [+]:
  Have you taken a look at this?
 
  Bug 7174 - Authentication rewriting
 
  It is not configuration file -driven, but it is almost 100% of what
  you described with some added bonuses.

 I haven't had a chance to yet, still trying to avoid getting sucked in
 to anything that's not elasticsearch related right now.

  With a looong list of complex dependencies.

 I sure hope you read my post about dependencies from a few months
 back :)

 In case you didn't:

 http://wiki.koha-community.org/wiki/Building_Debian_Dependencies/Dependency_Guidelines

 --
 Robin Sheat
 Catalyst IT Ltd.
 ✆ +64 4 803 2204
 GPG: 5FA7 4B49 1E4D CAA4 4C38  8505 77F5 B724 F871 3BDF

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Koha Hackfest in Berlin?

[Brendan Gallagher]

If there is a hackfest in Berlin - I could perhaps send someone from the US
to join in also.  We'll continue to go to the Marseille hackfest too.

Cheers,
Brendan

On Thu, Jul 9, 2015 at 1:00 PM, Mirko Tietgen mi...@abunchofthings.net
wrote:

 Fridolin Somers schrieb am 09.07.2015
  Looks great.
 
  Maybe indeed we could export the Marseille event, so we get more
  people at once.
  And it will be nice to see other cities (I go to Marseille each week)
 Thank you! But I have not been to Marseille yet! And I want to join
 the Hackfest there next year too. :) (Even though I can't stand
 cheese :D )

 Cheers,

 Mirko


 --

 Mirko Tietgen
 mi...@abunchofthings.net
 http://koha.abunchofthings.net
 http://meinkoha.de


 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Request for sign off...

[Brendan Gallagher]

CONFLICT (content): Merge conflict in installer/data/mysql/updatedatabase.pl

Auto-merging installer/data/mysql/sysprefs.sql

Auto-merging catalogue/detail.pl

Failed to merge in the changes.

Patch failed at 0001 Bug 5010 - Fix OPACBaseURL to include protocol

On Sat, Apr 18, 2015 at 3:28 PM, Mark Tompsett mtomp...@hotmail.com wrote:

   Greetings,

 I know it is big and scary, but could someone attempt to sign off bug
 5010? Thank you. [image: Smile]

 GPML,
 Mark Tompsett

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] plack in production

[Brendan Gallagher]

Great info Gaetan!

What does everyone feel about these tests?  Can we get a little feedback
here so that we can get some good bugs going?

The can't call method field I've seen before - but I have always chalked
that up to a bad MARC record.  (Please let's kill MARC ;)  we can do better
;)  )

The other ones I haven't seen before.

Thanks,
Brendan



On Fri, Apr 17, 2015 at 7:00 AM, Gaetan Boisson gaetan.bois...@biblibre.com
 wrote:

  Hello,

 we have tested plack a little further. We have achieved much more
 stability but are still encountering very serious bugs, before filing a
 report for each of them, i would like to ask here whether it does sound
 like something that is happening because of plack, and whether this has
 been identified before :

 - A vast majority of records are giving a The record you requested does
 not exist message when trying to display the detailed record, even though
 the record does seem to exist in the database, and i was even able to check
 out items linked to said record.
 - trying to place a reservation and a document from a result list results
 in an error, maybe unsurprisingly given the above :

 Can't call method field on an undefined value at
 /home/koha/src/C4/Items.pm line 1625.
  at /usr/share/perl/5.18/CGI/Carp.pm line 378

 - i noticed a delay between changing circulation rules and seeing them
 applied when checking out items (the rule was saying i could borrow 13
 items, i brought it down to 2, but was then able to checkout 3 items
 without getting a notice. Shortly after i was getting proper notices
 telling me i was exceeding the quota)
 - There were numerous encoding problems with non ascii characters, this
 might be linked to Bug 13815 - plack loose CGI qw(-utf8) flag creating
 incorrect utf-8 encoding everywhere; but this was not just patrons.
 Cataloging frameworks, authorised values, fund names were all affected.
 - exporting data from cgi-bin/koha/tools/export.pl also lead to a crash,
 which seems to be linked to UTF-8 issue too:

 :11: parser error : Input is not proper UTF-8, indicate encoding !
 Bytes: 0x80 0x3C 0x2F 0x73
 subfield code=p5.40�/subfield
^
  at /home/koha/src/tools/export.pl line 683

 Let me know what seems geniunely new and plack related to you and i will
 file the bugs.

 Thanks!


 Le 26/03/2015 16:17, Gaetan Boisson a écrit :

  Hello all,

 we have been talking about plack quite a lot in the last hackfest, and i
 must say i am not that comfortable with the technical aspects and hardly
 understand what the issues are, but...

 I tried it with the help of our sysops a couple days ago, and i must say
 koha does feel *really* fast with plack enabled. If you havent yet, you
 should try. It really made me realize why this should be a priority for us
 to get it to work.

 Now, it turns out it really doesn't work for us. It keeps crashing every
 few minutes. We haven't had time to investigate any further, but before
 pouring more time in this i wanted to know whether anyone was using it
 seriously (including for the staff interface), and what your conclusions
 are. Importantly, i would also like to know more about the recommended
 configuration, and the areas we should have a close look at in our set up.

 Thanks for your advice!


 --
 Gaetan Boisson
 Chef de projet bibliothécaire
 BibLibre
 06 52 42 51 29
 108 avenue Breteuil 13006 Marseille
 gaetan.bois...@biblibre.com

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] New RESTful API

[Brendan Gallagher]

Any further comments on the New RESTful API stuff?  We are moving forward
with that.  We should have some work from Biblibre in the next few days
(7~10) max.  I'd be interested in knowing who would like to help test this
all?

Cheers,
Brendan

On Tue, Mar 10, 2015 at 1:40 PM, Chris Cormack chr...@catalyst.net.nz
wrote:

 * Tomas Cohen Arazi (tomasco...@gmail.com) wrote:

  Raisin was the first proposed tool to build the API. We found it was
  Plack-only, and that it implemented an outdated version of Swagger, which
  seemed a requirement for people proposing it.
 
  Mojolicious was found to be CGI-friendly, and also has a Swagger2 plugin.
 
  I'm not saying those are blockers, but that was part of the discussion.
 
 Excellent thanks, that's the information I was after

 Chris


 --
 Chris Cormack
 Catalyst IT Ltd.
 +64 4 803 2238
 PO Box 11-053, Manners St, Wellington 6142, New Zealand

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Calling for volunteers to join the sub-committee for the Koha Fund!

[Brendan Gallagher]

Please excuse the cross-posting...  (Please share this with others beyond
these two lists - Thank you kindly)

Calling for volunteers to join the sub-committee for the Koha Fund!

What I propose is that those that volunteer for the sub-committee would
volunteer for a 1 year term.

*Immediate responsibilities* would include creating the by-laws that the
sub-committee would act by.  This would include taking the lead on creating
a document (in an open forum) that would be presented to the Koha community
for a vote of acceptance, at least one week before the next general meeting
(7 days).  Allowing for time for comments on the document and others to
read the document, so that the document could be adjusted and corrected in
time for a vote at the general meeting.
**One note here is that if there is a bylaw that would potentially exclude
one of the original volunteering sub-committee members (who knows right),
that they would willingly step-down once the by-laws are completed (OR is
that really a worry and we just really need to make sure we have enough
volunteers to get a committee?)**

Once the by-laws have been accepted by a majority vote in a general
meeting, then the original volunteer members, would serve the rest of the
year as part of the sub-committee for the Koha-fund.  The main purpose of
the sub-committee is to creatively raise money for Koha to be spent on Koha
(most likely to begin money would be spent on sign-offs, QA-time, bugzilla
maintenance cleaning, for example right now we have 26 critical bugs with
no patch (so do those really need a patch or does bugzilla really need to
be cleaned up?) ).  So those that are interested in joining this to help
make the bylaws so this is a successful venture and then being an active
advocate for the Fund - please join up.  You do not need to be a developer
or anything close to that.

I propose that we leave the volunteering open until 1 week before the next
general meeting which is 8 April 2015 at 19:00 UTC.  That should give
people enough time to add their names here --
http://wiki.koha-community.org/wiki/Fundraising ...  Look at the Fundraising
Committee section for a place.  Then at the general meeting April 8th we
can vote on the names present and then move forward.

So Dates...

Starting now, until April 1st --- people place their names on the wiki list
for being a potential volunteer for the sub-committee  (I would also be
willing to keep this open until April 7th if others agree to that)

April 1st to April 8th --  Community has a chance to review the names on
their own time and be prepared for voting at the general meeting.

April 8th - Sub-committee volunteers are confirmed...

Please don't hesitate to ask any question at all, the more we have before
we vote on April 8th the better and more prepared everyone will be!  (no
surprises)

Cheers and Thank much,
Brendan Gallagher (bag)




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Roles for 3.22 - will be voted on at next General Meeting April 8th

[Brendan Gallagher]

Hello All -

Just a reminder -
http://wiki.koha-community.org/wiki/General_IRC_meeting_8_April_2015

8 April 2015 at 19:00 UTC

On the agenda we have Roles for 3.22...  Please if you are volunteering for
a position for the future release, please fill in the wiki-page (
http://wiki.koha-community.org/wiki/Roles_for_3.22 ).  The sooner the
better so that everyone has sometime to read any proposals or even just see
who is volunteering for what.  Those of you that are wishing to continue in
the same role that you are in, please don't forget to fill out the wiki
page.

Thanks much,

Brendan Gallagher

--
---
Brendan A. Gallagher
ByWater Solutions
CEO
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Interlibrary Loans RFC

[Brendan Gallagher]

Thanks Alex,

After reading I don't have any comments - besides I'm ready to help test
what you bring forward.

Cheers,
Brendan

On Sunday, March 15, 2015, Alex Sassmannshausen 
alex.sassmannshau...@gmail.com wrote:

 Hello,

 I've now been able to draft a first version of an Interlibrary Loans
 Module for Koha RFC.

 You can find it at http://wiki.koha-community.org/wiki/ILL_Module.

 For the purposes of this work I have usurped bug number 7317.

 The RFC is based on work that I, as part of PTFS Europe am carrying out
 for our customers, and on discussions that we had at the hackfest.

 There are 2 primary concerns for this module from my perspective:
 1) provide all the functionality our customers require
 2) make the module generic enough so that we can implement different
'backends' that would service different ILL workflows/systems.

 Feedback (both on style and content), welcome.

 Best wishes,

 Alex


 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org javascript:;
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/



-- 
Sent from Gmail Mobile
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] New RESTful API

[Brendan Gallagher]

Just adding in - great communication everyone.  Love watching that.

Cheers,
Brendan

On Tue, Mar 10, 2015 at 9:40 PM, Chris Cormack chr...@catalyst.net.nz
wrote:

 * Tomas Cohen Arazi (tomasco...@gmail.com) wrote:

  Raisin was the first proposed tool to build the API. We found it was
  Plack-only, and that it implemented an outdated version of Swagger, which
  seemed a requirement for people proposing it.
 
  Mojolicious was found to be CGI-friendly, and also has a Swagger2 plugin.
 
  I'm not saying those are blockers, but that was part of the discussion.
 
 Excellent thanks, that's the information I was after

 Chris


 --
 Chris Cormack
 Catalyst IT Ltd.
 +64 4 803 2238
 PO Box 11-053, Manners St, Wellington 6142, New Zealand

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] [Koha] Koha development

[Brendan Gallagher]

Marshall -

I think we are all curious to what you are going to say here?

Thanks,
Brendan

On Mon, Feb 16, 2015 at 12:21 AM, Magnus Enger mag...@libriotech.no wrote:

 Hi!

 On 12 February 2015 at 15:07, Marshall Breeding
 marshall.breed...@librarytechnology.org wrote:
  Could each of the support firms or individuals involved in Koha
 development
  please either post to this list or send to me individually the FTE that
 you
  or your organization contributes for each of the major categories of
  activity?

 Libriotech is (so far!) a one man band, I am the sole employee. That
 is the easy part.

 In 2014 I held a temporary part time position at Oslo Public Library,
 so all my work on Koha was done on their time.

 In 2015 I plan to do some development and some QA and contribute to
 the Koha wiki. Maybe, if I'm lucky, I can achieve this:

 Development: 4-50%
 QA: 10%

 But I also have customers I need to keep happy, so only time will tell
 how it actually turns out...

 Best regards,
 Magnus Enger
 Libriotech
 ___
 Koha mailing list  http://koha-community.org
 k...@lists.katipo.co.nz
 http://lists.katipo.co.nz/mailman/listinfo/koha




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Sign off request

[Brendan Gallagher]

I will take a look.

So far I have applied and run the QA test (and yes all is good).  This is a
big, so it will take me a few days to get through.  I am interested - if
others have an idea on how we could break this up (If not give me a few and
I'll slug through it)?

Thanks,
Brendan



On Wed, Feb 18, 2015 at 4:09 AM, Marcel de Rooy m.de.r...@rijksmuseum.nl
wrote:

  Hi all,

 Need some help: Anyone willing to sign off on report 10480: Improvements
 for framework plugins in cataloguing/item editor ?



 Patches submitted on Dec 11, once rebased, still apply.



 Thx,



 Marcel

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] [Koha] Koha development

[Brendan Gallagher]

Oh that is an excellent point.  So Koha is installed in 10 thousand
(10,000) plus libraries around the world (considering there are 1000+ in
Turkey and 1000+ in Argentina, just to name two large concentrations of
installations) .  Maybe other systems have that too, but man everyone who
works with Koha - that's a really great number.  So a BIG PAT on everyones
back - that's just awesome.

On Fri, Feb 13, 2015 at 6:30 AM, Tomas Cohen Arazi tomasco...@gmail.com
wrote:

 I think it will all depend on how you read the numbers.

 If a project has (say) a third of the developers another project has, but
 has the amount of institutions using it, Koha has, it is a point won by the
 project. If the feature set is equal or better, then those numbers become
 more and more in favor of the project.

 That said, I'm not sure how the FTE measuring model serves to what
 purpose. I guess it will depend on marketing guys using the numbers one way
 or the other.

 In any case, I'm intrigued by this measures, because I'm confident Koha
 would show really interesting numbers ;-)



 On Fri, Feb 13, 2015 at 10:55 AM, Paul Poulain paul.poul...@biblibre.com
 wrote:

  Le 12/02/2015 22:14, Marshall Breeding a écrit :

  Brendan,



 Some personnel FTE numbers from last year can be seen on the tables from
 the Library Systems Report:


 http://www.americanlibrariesmagazine.org/sites/americanlibrariesmagazine.org/files/content/Charts_MarshallBreeding.pdf



 The numbers are for the company overall, and not limited to efforts
 expended on specific products or projects.



 I 10% agree with what other have said ! We differ so much from
 proprietary vendors that comparing is a hazardous thing. Do you have the
 answer to the following question: is 2km bigger or smaller than 3kg ?

 Additional thought: I feel that, once again, I have missed the marketing
 speech in my answer (3FTE). I should have said 10 !
 Marshall, what you must understand is that we've no marketing guy in our
 project (at least on koha-devel mailing lists). Most of us (all of us ?)
 don't care of being bigger/more beautiful/higher/... than others. We focus
 on product and development. What we love is hacking, not selling/promoting.
 The consequence is that you'll compare numbers given by marketing guys vs
 numbers given by tecchie guys (I'm not implying that marketing guys lie.
 But we don't have the same way of understanding/explaining things. Once
 again 2km vs 3kg... )

 Just one example: at the beginning of BibLibre, we were counting Aix
 Marseille university as one library (it's obvious, that's one contract).
 Then we realized that other were counting differently. So now we count Aix
 Marseille as 57 libraries (it's obvious, it's a university with 57
 different libraries).
 But as we're still honest, scientists, and we prefer valid  verifiable
 numbers. So we usually say BibLibre support more than 500 libraries
 through 100+ contracts ;-)

 Another example : compare my presentation made at KohaCon and the one
 made by Alvet (from Ebsco) : one was basic, the other was fancy. We will
 probably never reach such a quality in terms of fanciness. That's probably
 a weakness, but I'm sure that's also a strength: we want nothing less than
 changing the way ppl do business ;-) 2kg and 3km ...

 OK, stopping to behave as the old wise man, back to working ;-)

 --
 Paul Poulain, Associé-gérant / co-owner
 BibLibre, expert du logiciel libre pour les bibliothèques
 BibLibre, Open Source software for libraries expert


 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




 --
 Tomás Cohen Arazi
 Prosecretaría de Informática
 Universidad Nacional de Córdoba
 ✆ +54 351 5353750 ext 13168
 GPG: B76C 6E7C 2D80 551A C765  E225 0A27 2EA1 B2F3 C15F

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : 

Re: [Koha-devel] [Koha] Koha development

[Brendan Gallagher]

I would be much happier using the numbers that Tomás pointed out (which is
a much different story then FTE).  Marshall could you maybe ask these
proprietary companies to match our numbers, instead of the other way around
- then you'd get a much better idea of what's actually happening.

For example, we have about 3000 patches submitted a year from close to 100
different authors.  Let's just say that it's 6 hours average to write and
submit the patches (so we are at 18,000 hours there), then it's 3 hours
average to sign off the patches (9,000 hrs), then 3 hours average to QA the
patches (another 9,000 hrs).   Thats 9 FTE right there (and that's being
generous with my averaging - also those FTE aren't checking facebook etc ;)
)   And that is only a small portion of the whole picture, I haven't even
gotten into the RMs or RMaints responsibilities or anything that goes with
packaging the release, then we've got all the documentation people too.  OR
even the amount of time to manage such large amounts of code (which I'm
sure the proprietaries are counting in their results).

Please anyone adjust my numbers above and I'm only just really guessing and
the amount of time to write the patches in the first place should could
needs to be doubled to 12 hours on average.

Just some food for thought.  Also we'd be interested in what the
blackbox/closed systems are reporting for your question?

On Thu, Feb 12, 2015 at 9:31 AM, Tomas Cohen Arazi tomasco...@gmail.com
wrote:

 I'm not sure how to count it either. This would be my estimate.

 I spend 50% of my time doing Release Manager duties, the rest is spent
 working on development and documentation. But if I count the amount of
 hours I work for Koha, I should count a total of 1.3 FTE, I guess. If I
 count Bernardo, it'd be something like:

 Universidad Nacional de Cordoba (Tomas + Bernardo)
 Quality Assurance: 0.6 FTE + 0,1 FTE = 0.6 FTE
 Development: 0.5 FTE + 0.1 FTE = 0.6 FTE
 Documentation:  0.2 FTE

 Community participation is difficult to count.

 I'm interested on the numbers you can collect. My hypothesis would be that
 more development allocation is available than most proprietary ILS
 products. Of course it fluctuates every year, but the OpenHub numbers speak
 of themselves 88 contributors for 2014. Unfortunately I cannot find a way
 to get the COCOMO-model invested working hours.

 Good luck, Marshall!


 On Thu, Feb 12, 2015 at 2:17 PM, Marshall Breeding 
 marshall.breed...@librarytechnology.org wrote:

 Paul,

 This estimate helps quite a bit.  Part of what I'm working toward is
 being able to have a figure for Koha that corresponds to what the vendors
 developing proprietary products allocate to product development.  They also
 have lots of staff devoted to things like marketing and administration, but
 the point of comparison is the FTE allocated to development.  My hypothesis
 is that the overall development allocation for Koha is similar to that for
 proprietary ILS products and I hope to be able to document that to some
 degree.

 -marshall



 -Original Message-
 From: koha-devel-boun...@lists.koha-community.org [mailto:
 koha-devel-boun...@lists.koha-community.org] On Behalf Of Paul Poulain
 Sent: Thursday, February 12, 2015 11:03 AM
 To: k...@lists.katipo.co.nz; koha-devel@lists.koha-community.org
 Subject: Re: [Koha-devel] [Koha] Koha development

 Le 12/02/2015 15:07, Marshall Breeding a écrit :
  To the Koha development community,
 Hi Marshall,
  Could each of the support firms or individuals involved in Koha
 development please either post to this list or send to me individually the
 FTE that you or your organization contributes for each of the major
 categories of activity?
 
 Really : it's impossible to evaluate properly.
 some numbers can be evaluated, some can't.

 For example, BibLibre :
   * has Jonathan working full time on Koha. Half time dedicated to the
 community, half time dedicated to development sponsored by customers (but
 still on Koha, and for a direct benefit of the Koha community). So, OK,
 jonathan = 1 FTE
   * has Fridolin being Release Maintainer. He releases a version every
 month (4 hours to package it, roughly), plus a variable number of hours to
 push patches (between 1 and 10 ? it depends on what is waiting to be
 pushed. Let's say an average of 5 hours). 1 version every month, 9 hours
 per version = 9*12 = 118 (this number is wrong, it's an estimate)
   * has a support team of 3 (including fridolin), that regularly submit
 bugfixes. Frankly, we don't count the specific time dedicated to fixing a
 bug and submitting a patch vs the time dedicated to the customer.
   * has other developers regularly submitting patches (julian, matthias,
 ...)
   * has me ... who does not submit patches anymore, but I'm trying to
 organize all the work at BibLibre, do some non-dev things for the
 community. Should I count this ? I think yes, because (I hope), the project
 also move through non technical work.
   * has all our 

Re: [Koha-devel] [Koha] Koha development

[Brendan Gallagher]

Now that we have a better idea of the answer you are looking for.

Roughly estimating all companies that support Koha (12 of them in India, 6
in Spain alone) I'd say Koha is 1500+ easily.

On Thu, Feb 12, 2015 at 1:22 PM, Chris Cormack ch...@bigballofwax.co.nz
wrote:



 On 13 February 2015 at 10:14, Marshall Breeding 
 marshall.breed...@librarytechnology.org wrote:

  Brendan,



 Some personnel FTE numbers from last year can be seen on the tables from
 the Library Systems Report:


 http://www.americanlibrariesmagazine.org/sites/americanlibrariesmagazine.org/files/content/Charts_MarshallBreeding.pdf



 The numbers are for the company overall, and not limited to efforts
 expended on specific products or projects.




 In that case for Catalyst there are 235 staff, of which 182 are devs

 Chris




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] [Koha] Koha development

[Brendan Gallagher]

And that misses the point, That's just companies - were a majority is
volunteer time.  Like Chris is paid to work on Koha 1 FTE, but that's only
about 1/2 of the amount of time he works on Koha, easily another 40 hours a
week is all completely volunteer.

Good difficult questions Marshall (you totally got me thinking today - I
love it) - I don't think the project will ever be fairly compared.  I'd
just say the open source project rocks all by itself ;)



On Thu, Feb 12, 2015 at 1:24 PM, Brendan Gallagher 
i...@bywatersolutions.com wrote:

 Now that we have a better idea of the answer you are looking for.

 Roughly estimating all companies that support Koha (12 of them in India, 6
 in Spain alone) I'd say Koha is 1500+ easily.

 On Thu, Feb 12, 2015 at 1:22 PM, Chris Cormack ch...@bigballofwax.co.nz
 wrote:



 On 13 February 2015 at 10:14, Marshall Breeding 
 marshall.breed...@librarytechnology.org wrote:

  Brendan,



 Some personnel FTE numbers from last year can be seen on the tables from
 the Library Systems Report:


 http://www.americanlibrariesmagazine.org/sites/americanlibrariesmagazine.org/files/content/Charts_MarshallBreeding.pdf



 The numbers are for the company overall, and not limited to efforts
 expended on specific products or projects.




 In that case for Catalyst there are 235 staff, of which 182 are devs

 Chris




 --

 ---
 Brendan A. Gallagher
 ByWater Solutions
 CEO

 Support and Consulting for Open Source Software
 Installation, Data Migration, Training, Customization, Hosting
 and Complete Support Packages
 Headquarters: Santa Barbara, CA - Office: Redding, CT
 Phone # (888) 900-8944
 http://bywatersolutions.com
 i...@bywatersolutions.com




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Proposal for fund raising for Koha - to discuss/vote at December General Meeting.

[Brendan Gallagher]

.


*Avenues for Fund Raising:*

Donate money now button on the homepage of Koha - and code for that button
will be made available for anyone to put that on their own home pages, etc.

Reach out to all support companies that are listed on the Koha community
website for donations to help seed the fund.

Board members from around the world will be responsible for leading
local/regional fund raising campaigns

Board members will pursue and write grant proposals for alternative fund
generation.  Think Mellon grants here.

This paper is presented to the community for endorsement of the idea, so
that we can move forward promptly toward this goal.  Let's definitely
discuss during the December General Meeting and we can vote then or if the
community decides - vote in January.  This will only be a vote on YES move
forward, NO do not do this (nothing about structure etc.).

Regards,
Brendan Gallagher, Bob Birchall and Paul Poulain
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Fwd: Questionaire regarding Patron Privacy and Security

[Brendan Gallagher]

Can someone add info about LDAP to that list?  (someone with the correct
technical terms that is ;) )

On Mon, Nov 10, 2014 at 11:50 AM, Chris Cormack ch...@bigballofwax.co.nz
wrote:

 Forwarded with Marshall's permission

 Would you be able to help me fill this out?

 Galen has already made a good start which I have pasted at
 https://etherpad.mozilla.org/YiC0J8efmw

 Also the Evergreen community are working on their response at

 https://docs.google.com/document/d/1RgTnQOITvm3B_yzBOTfAuPZgDZig7xQ3N7Euib8rONc/edit

 Thanks

 Chris

 -- Forwarded message --
 From: Marshall Breeding marshall.breed...@librarytechnology.org
 Date: 11 November 2014 02:55
 Subject: Questionaire regarding Patron Privacy and Security
 To: Chris Cormack ch...@bigballofwax.co.nz


  As you know, libraries are increasingly concerned with protecting the
 privacy of their patrons and in strong security.  For an upcoming panel
 for CNI I have been charged with gathering data regarding how library
 management systems handle patron privacy and security.



 It would be great if I could have responses by November 21, 2014.



 Could you provide responses for the Koha?  You are the one that comes to
 mind among those in the Koha community, but if there is someone else that
 you think should respond, please let me know. I really appreciate your help.




 I am interested in gathering some information regarding the current
 capabilities or options that systems offer today, looking forward to
 further progress in this arena toward more secure treatment of
 patron-related transactions.  Given increasing concerns, I would expect
 that each company is working on providing a more secure environment.



 This data initially will be used for a briefing at the upcoming CNI Fall
 2014 Membership Meeting, December 8-9, 2014:


 http://www.cni.org/events/membership-meetings/upcoming-meeting/fall-2014/project-briefings-breakout-sessions/



 I also anticipate that this information would be helpful for other
 discussions, presentations, or reports.



 In addition to information provided by the developers of systems, I may
 also work with systems administrators of the various products for their
 perspectives on these security-related capabilities and options.



 I would greatly appreciate it if you could have your technical or product
 managers provide responses to these specific questions.  It would also be
 helpful to have any additional comments or perspective whether these seem
 to be the best areas of concern regarding patron privacy, if there are
 alternative strategies that you are pursuing.  I would also be interested
 to hear whether this topic has been raised also by your customers or users
 through enhancement requests or other product roadmap priorities.



 Does your online catalog or discovery interface:

 · Enforce encryption through SSL for all transactions involving
 patron activity

 · Offer the library an option to enable SSL for all transactions
 involving patron activity

 · Enforce encryption for specific pages or transactions involving
 patron details or login credentials

 · Offer the library an option to enable SSL for specific pages or
 transactions involving patron details or login details



 Does your client or interface for delivering functionality to library
 personnel:

 · Enforce encryption through SSL or other encryption mechanisms
 for all transactions

 · Offer the library an option to enable SSL or other encryption
 mechanisms for all transactions

 · Enforce encryption for specific pages or transactions involving
 patron details

 · Enforce Encryption for specific pages involving authentication
 of library personnel accounts

 · Offer the library an option to enable SSL for specific pages
 involving patron details

 · Offer the library an option to enable SSL or other encryption
 mechanisms for specific pages involving authentication of library personnel

 · Enforce encryption for transactions involving institutional
 financial data (acquisitions, patron fines, etc)

 · Offer the library an option to enable SSL or other encryption
 mechanisms for financial transactions



 How does your platform or system deal with the security of the storage of
 specific types of data:

 · Does your system store patron passwords or PINs as unencrypted
 text

 · Does your system store patron passwords or PINs as salted hash
 or similar mechanisms

 · Does your system encrypt patron details as they are recorded
 and stored?



 Are logs or other system files that include patron search or reading
 behaviors encrypted?



 Describe any other security measures in place that protect patron privacy
 as it is transmitted over local networks or the Internet from interception
 by any third party.  One specific scenario that has been a topic of concern
 involves the presentation of e-book discovery and 

Re: [Koha-devel] hea.koha-community.org

[Brendan Gallagher]

Sweet!  Really cool

On Tuesday, October 21, 2014, Paul Poulain paul.poul...@biblibre.com
wrote:

 Le 21/10/2014 15:07, Paul Poulain a écrit :

 In the next weeks, we will submit the patch to bugzilla, and I hope it
 will be quickly signed, QAed and pushed.


 mmm... in fact it is already : http://bugs.koha-community.
 org/bugzilla3/show_bug.cgi?id=11926 ...

 (and passed QA, so, Tomas, the ball is in Cordoba :D)

 --
 Paul Poulain, Associé-gérant / co-owner
 BibLibre, expert du logiciel libre pour les bibliothèques
 BibLibre, Open Source software for libraries expert
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/



-- 
Sent from Gmail Mobile
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Proposal for a change in guidelines for the sign-off process in the Koha-community

[Brendan Gallagher]

I agree these are good ideas.  We have done these many times, but the
follow-through just never really happens.

I guess I'm more pointing out we've (we've = koha-community) got a problem
with the current process.  We have more patches than we have as a
collective volunteer time within the community to keep up with the
demand.  The main point is we need more people in the community (one way to
achieve that is to not limit the pool of potential community members
signing-off on bugs - that's what I'm proposing).  Everyone that attended
the hackfest did not have any major problems with what we talked about - it
was really an attitude of Let's try it and see what happens (some thought
it would help and others just weren't sure it would really make a
difference or not).  I am excited to give it a try.

We've changed our process a little and we find some libraries that will use
a major feature in a production environment (a very small group, cause we
try to keep everyone on the main releases of Koha), so once they have used
it for awhile, we get them to sign-off on the bug.



On Wed, Oct 15, 2014 at 7:27 AM, Heather Braum (NEKLS) hbr...@nekls.org
wrote:

 I don't want to weigh in on the overall discussion around these changes,
 but I thinkOwen's point about a setting up a separate test instance to test
 major features like his example of bug 6427 is a very good idea, and would
 allow many people to test it thoroughly, in a more robust, almost live
 environment. The more eyes on something this critical, the better,
 especially if you involve librarians at the circulation desk who deal with
 this part of the system many, many times a day. But having a test system
 these people can access is the key -- they aren't normally engaged in the
 community, but you know they know the fining system, and want to see it
 work.

 My organization has been waiting for this development for over a year now,
 and I can think of several people at our libraries that I'd be willing to
 volunteer to do some thorough testing if something like this was set up.

 Heather Braum
 NExpress Coordinator
 Resource Sharing Librarian
 Northeast Kansas Library System
 hbr...@nekls.org

 The illiterate of the 21st century will not be those who cannot read
 and write, but those who cannot learn, unlearn, and relearn. ~Alvin
 Toffler, *Rethinking the Future*




 On Wed, Oct 15, 2014 at 7:23 AM, Owen Leonard oleon...@myacpl.org wrote:

  I'd like to put forward a motion for removal of the guideline that one
  company shouldn't sign-off on the same company's patches within the
  community.

 I think this is a good rule, and I think our current process has
 proved that by showing that with many different points of view looking
 at the code more issues can be found which need to be addressed before
 something is ready.

 I realize how frustrating it is to have something big and hard to test
 languish in the QA process, but I think the right solution might be to
 get more creative about how to help things move along.

 From my perspective as a bug tester the biggest thing I can say about
 it is to have good test plans. I mean really really good test plans.
 List, explicitly, every possible step that the tester could take to
 test the patch.

 The obvious example here is Bug 6427 - Rewrite of the accounts system
 (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6427). A big
 patch that touches a LOT of files and involves one of the most
 mission-critical aspects of Koha's circulation functionality. Pushing
 it before it was properly tested could be disastrous for libraries who
 collect fines throughout the day.

 The bug has a pretty good test plan, but is that enough? What else
 could we do to make sure it's ready for production? Perhaps set up a
 dedicated test instance with some good sample data, give out logins
 which give permission to circulate and collect fines, assign multiple
 days' worth of tests to be performed by multiple testers?

 Getting volunteer testers is hard, and getting multiple volunteer
 testers is harder, but sometimes I think we need to take a more active
 hand in soliciting and promoting testing.

   -- Owen

 --
 Web Developer
 Athens County Public Libraries
 http://www.myacpl.org
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/



 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater 

Re: [Koha-devel] Proposed addition to the development-meetings:

[Brendan Gallagher]

Hello Marcel -


I feel that some things that are put into discussion just take too long to
get out of discussion or don't really ever get any feedback.  So the idea
is that I'll bring these up at Dev-meetings so we get some movement on
them.  The example I used was the DBIC - we've been talking about this for
a few years now and I think it's time we all vote and decide on the correct
path forward.  That is it - nothing more complicated than that.

Thanks,
Brendan

On Mon, Oct 13, 2014 at 12:52 AM, Marcel de Rooy m.de.r...@rijksmuseum.nl
wrote:

   Along with the first homework assign I will also be setting a date for
 us to vote on the (homework)

  bug/enh/thought at the meeting after a sufficient discussion has
 occurred.

 Brendan: What do you exactly mean here? The bug/enh thought is kind of
 vague :)

 There will always be discussion if some patch is just a bugfix or an
 enhancement. Ideally, every bug fix should be an enhancement. And what
 about the difference: enhancement vs. new feature?



 Marcel

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Proposal for a change in guidelines for the sign-off process in the Koha-community

[Brendan Gallagher]

HI Marcel -

I think most everyone that was in attendance thought differently then those
guidelines.  Some said 3 months others said not at all, etc etc.  So I'm
just bring this up so that everyone is on the same page and changing the
guideline so that there isn't a 1 month wait period.  (Yes it is evident
that communication in the community is lacking)

Thanks,
Brendan

On Mon, Oct 13, 2014 at 12:45 AM, Marcel de Rooy m.de.r...@rijksmuseum.nl
wrote:

   I'd like to put forward a motion for removal of the guideline that one
 company shouldn't sign-off on the same

  company's patches within the community.  I am suggesting additional
 checks be included in the sign-off process

  to prevent abuse of the proposed guideline, such as the committer and
 the person signing off must not have

  collaborated on the development of the patch.

 See: http://wiki.koha-community.org/wiki/Development_workflow

 These workflow rules on the wiki already say:

 *Preferably*, patch writer and patch signer should not be from the same
 company or institution.

 Yes, it is preferred but is not strictly required.

 And also:

 If a patch is not passed QA for one month, then it can be QA'd by someone
 from the same company or institution.



 I would suggest to make the following change:

 If a patch has not been signed for one month, it can be signed off by
 someone from the same company or institution. (Easy to check by QAer.)

 And to prevent abuse of the combination (signoff and QA in the same
 company):

 If a patch has not passed QA for one month, then it can be QA'd by someone
 from the same company or institution UNLESS it is already signed by someone
 from the same company. (Does this rule need a sort of escape to prevent
 very specific patches waiting for several months in the SO queue?)



 Marcel



 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Proposal for a change in guidelines for the sign-off process in the Koha-community

[Brendan Gallagher]

Hello All -

During the hackfest, there was a discussion on the sign-off process for
Koha.  In attendance was, Nathan, Chris, Katrin, Paul_P, Jonathan, Arnaud,
Joy, Brendan, Tomás, Brooke, Tom, and BobB.  Here is what we all agreed
upon to send a proposal to the next developers or general meeting

I'd like to put forward a motion for removal of the guideline that one
company shouldn't sign-off on the same company's patches within the
community.  I am suggesting additional checks be included in the sign-off
process to prevent abuse of the proposed guideline, such as the committer
and the person signing off must not have collaborated on the development of
the patch.  We shall review that idea/process every 6 months as an agenda
item in the general meeting, to make sure that no abuse of the new
privilege has occurred; also note here - that we do not have to wait 6
months to point out abuse of this new privilege.  The QA team and Release
Team still have the right to ask for more eyes to look at a certain bug at
anytime and this should continue.

Thank you,
Brendan Gallagher
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Proposed addition to the development-meetings:

[Brendan Gallagher]

Hello All -

I'd like at have an addition to the development-meeting.  The idea is that,
I would present some of the older bugs or even some new ones that really
need to have a discussion that results in a solid agreed upon path
forward.  For example we have 2~3 methods for using DBIC for Koha code
where we really need to decide on one path and move forward with that
design.

The method that I would like to add to the dev-meetings is that I will
bring up certain topics at a development-meeting as a homework assign, so
that we can all discuss that idea/bug/thought at the next meeting.  Along
with the first homework assign I will also be setting a date for us to vote
on the (homework) bug/enh/thought at the meeting after a sufficient
discussion has occurred.

The main goal here is to set some deadlines for some of these larger
discussions so that we can all move forward.  Any meetings that I know I
will miss I will find a representative to fulfill this role at the
development-meetings.

Thanks,
Brendan Gallagher
ByWater Solutions
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Proposal for a change in guidelines for the sign-off process in the Koha-community

[Brendan Gallagher]

One Additional note -

I would continue to encourage all those that sign-off on bugs to really add
a lot of notes to their sign-offs.  The more information on places that you
may have been stuck or parts you were not 100% sure on - really really help
the QA and RM teams.  That is totally one thing that I need to get better
at during my sign-offs and testing periods.

Thanks,
Brendan

On Fri, Oct 10, 2014 at 8:10 AM, Brendan Gallagher 
i...@bywatersolutions.com wrote:

 Hello All -

 During the hackfest, there was a discussion on the sign-off process for
 Koha.  In attendance was, Nathan, Chris, Katrin, Paul_P, Jonathan, Arnaud,
 Joy, Brendan, Tomás, Brooke, Tom, and BobB.  Here is what we all agreed
 upon to send a proposal to the next developers or general meeting

 I'd like to put forward a motion for removal of the guideline that one
 company shouldn't sign-off on the same company's patches within the
 community.  I am suggesting additional checks be included in the sign-off
 process to prevent abuse of the proposed guideline, such as the committer
 and the person signing off must not have collaborated on the development of
 the patch.  We shall review that idea/process every 6 months as an agenda
 item in the general meeting, to make sure that no abuse of the new
 privilege has occurred; also note here - that we do not have to wait 6
 months to point out abuse of this new privilege.  The QA team and Release
 Team still have the right to ask for more eyes to look at a certain bug at
 anytime and this should continue.

 Thank you,
 Brendan Gallagher




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Ajax datatables. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11703

[Brendan Gallagher]

Thanks Jonathan -

I see that you did do some testing on this.

Excellent!
Brendan


On Wed, Jun 25, 2014 at 4:30 AM, Jonathan Druart 
jonathan.dru...@biblibre.com wrote:

 Hi Brendan,

 I will try to have a look at the last patches and see if no regression
 is introduced.
 Hopefully I will have the time soon...

 Cheers,
 Jonathan

 2014-06-24 18:22 GMT+02:00 Brendan Gallagher i...@bywatersolutions.com:
  Hello QA -
 
  http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11703
 
  We just had a few little follow up's on the QA and we've completed those
  about a month ago and need a little QA follow up.  They do apply cleanly
  currently.  Anything I can do to help encourage someone to look at those
  last 2 follows and passed them for QA?  I'd love to get this into 3.16.1
 or
  3.16.2 ASAP.
 
  Thanks,
  Brendan
 
  --
 
 ---
  Brendan A. Gallagher
  ByWater Solutions
  CEO
 
 
  ___
  Koha-devel mailing list
  Koha-devel@lists.koha-community.org
  http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
  website : http://www.koha-community.org/
  git : http://git.koha-community.org/
  bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Ajax datatables. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11703

[Brendan Gallagher]

Hello QA -

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11703

We just had a few little follow up's on the QA and we've completed those
about a month ago and need a little QA follow up.  They do apply cleanly
currently.  Anything I can do to help encourage someone to look at those
last 2 follows and passed them for QA?  I'd love to get this into 3.16.1 or
3.16.2 ASAP.

Thanks,
Brendan

-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Koha Community Newsletter: May 2014

[Brendan Gallagher]

Hello -

The link for me - resolves to the April Newsletter.

http://koha-community.org/koha-community-newsletter-may-2014/   Try that
one.

-Brendan


On Wed, Jun 4, 2014 at 10:48 AM, Koha News kohan...@gmail.com wrote:


 Fellow Koha users:

  The Koha Community Newsletter for May 2014 is here:
 http://koha-community.org/koha-community-newsletter-may-2014/
 http://koha-community.org/koha-community-newsletter-april-2014/

  Many thanks to all the folks who submitted articles and news to this
 month's newsletter.

  Please feel free to email us with any corrections or suggestions.

  Thanks!

  Chad Roseburg
 Joanne Dillon
 Editors, Koha Community Newsletter



 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Convert circ tables to AJAX - possible for 3.16.1 ?

[Brendan Gallagher]

Hello All -

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11703

So Kyle and Katrin have been working many many hours on getting the patch
referenced above to Pass QA.  The only problem is we ran out of time to
safely get this into the general release and have enough time for some good
thorough testing - If only we had another two weeks.

I would like to promote this as a performance bug fix and that should be
included in the first point release for 3.16 - 3.16.1...  Performance bugs
are perfectly acceptable for point releases and I think if we look at it
that way - we have 2 months to test this thoroughly.  It's passed PA and
Galen also added some additional comments - which Kyle did follow up on.

Thoughts?  We're actively testing this but we'd love more to test it.


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11703

Thank you very much,
Brendan

-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Architectural goals for 3.16

[Brendan Gallagher]

Some plans that ByWater (Kyle, Jesse, etc.) has for 3.16 (or at least make
sure our patches are out there).

Elastic Search - which Chris talked about.

New catalogers interface - which Jesse Weaver has been working on and we're
getting closer and closer to having that ready to submit.  (Jesse did a
quick demo at KohaCon in Reno).  I bug pianohacker daily on when that's
going to be submitted :)

Finishing the Plackifying of the staff-side so that it could be stably
used.

I would also like to see a big push of using DBIx::Class and I love the
comments from Galen about using Koha on PG (++).  We are more than willing
to help in that project Galen - please take advantage of us and let us know
what you'd need help on.  We will contribute in any way that we can.

Just some thoughts - and I'm sure we'll add to that in the coming months.



On Tue, Dec 10, 2013 at 1:11 PM, Chris Cormack ch...@bigballofwax.co.nzwrote:

 Hi All

 In addition to the goals Galen has mentioned.

 Catalyst and Bywater are working on adding ElasticSearch as an option
 for searching in Koha.
 It will of course not remove Zebra, but will provide the option of
 using it as a search tool instead.

 The brief plan is

 Write code, so that if ElasticSearch is selected, when a Biblio is
 modified the index is updated. This will not preclude the zebra code
 from running, so the zebra indices are still updated too. (This is
 mostly working now)

 Next, allow the Public Interface (OPAC in the old talk) to use
 ElasticSearch to do it's searches (sorta working)

 Then, implement a browse feature (in planning)

 Then, allow the staff catalogue to use ElasticSearch (not even started).

 (Probably only get this far for 3.16)

 Then move on to the authorities ..

 Then allow for fully ajax option for searching ...

 The plan is incremental increases, not breaking existing search, in
 fact not touching the zebra code at all, so that any time you could
 switch back and you would still have working searches.

 Maybe eventually it will be feature complete, including a z3950 and
 sru/sw server and we can make switching it on mean switching zebra
 off. But definitely not for 3.16.

 You can follow along at

 http://git.catalyst.net.nz/gw?p=koha.git;a=shortlog;h=refs/heads/elastic_search

 I push everything as I go, (I will tidy it up into neater patches
 before submitting of course)

 Also, big huge thanks to the Catmandu developers
 http://librecat.org/index.html  whose library I am making extensive use of
 http://search.cpan.org/~nics/Catmandu-0.8001/

 I even got a patch in
 https://github.com/LibreCat/Catmandu-MARC/commits/master
 And its in the latest version on CPAN already.

 I am sure we will make much more use of their code, for creating RDF etc
 also

 Ok, tangent finished :)

 Chris
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] ping Koha (developers) community

[Brendan Gallagher]

I guess my follow up would be.

Yes rebasing is frustrating and sucks a lot of time.  I don't know the
answers.  But I would like to ask.  What can we do better to get our
patches accepted faster?  (Is it really just sending Cait and Galen cookies
everyday?)...  There has got to be somethings that those devs who maybe
aren't feeling the same frustration can lets us all know?

-Brendan


On Mon, Dec 9, 2013 at 10:36 AM, Jonathan Druart 
jonathan.dru...@biblibre.com wrote:

 Hi everybody,

 I have been working on Koha code for 3 years now. And for the last 2
 years, I have been implied in the rebase of the BibLibre's patches and in
 the QA team. Many things have changed during this time. Koha is widely used
 throughout the world, and some great improvement have been made in the
 community workflow.
 However, I feel the need to share with you today my feelings and my
 frustration about our work methods.

 As I said, great improvements have been made in the patch integration
 workflow. Our process of validation and integration of the patches has lead
 to an improvement of the code. The respect of the basic coding rules - e.g.
 the indentation - makes the code easier to read and to understand, and then
 easier to modify. The unit test coverage has been expanded and we can now
 add new tests easily. It is also more secure to modify a core routine. All
 of these points are very positive to me: I enjoy developing in these
 conditions.

 But in parallel, I encounter difficulties with my patches queue. I try to
 spend time on every patch, to follow the coding guidelines and to produce
 clean and readable code, with unit tests. I try to write incremental
 patches, and understandable test plans (as far as my English level allows
 me to do...). I also try to QA as soon as I have spare time, and to rebase
 my patches as fast as possible not to block the signoffers.

 Concretely, the steps of the integration of a feature from my point of
 view as developer are: the customer orders a development. I start the
 development on the master branch (or a previous stable version). After
 several iterations, the customer agrees on the feature. I rebase the patch
 on a fresh master branch and I submit the patch in Bugzilla. I iterate with
 the signoffer and rebase the patch. At this time, the customer expects the
 feature to be in his production server. I then rebase the feature against
 his branch. The patch is finally signed after several months and several
 rebases against the master branch. This will usually need rebase and
 adjustment for the QA and/or the RM steps. When the customer version will
 be upgraded to the next release, I will once again adapt the feature - it
 may have differed from the initial feature.
 Sorry for this massive paragraph but the workflow is really as heavy as
 described (and this is the simple version...).

 The excessive duration of this integration process leads to several
 problems:
 - The developer is frustrated by these multiple rebases (trust me, it is
 really tiresome).
 - Regressions may be introduced following a badly fixed conflict
 - The development may need to be fully rewritten.
 - This is a lost of time not only for the developer, but also for the
 signoffer and the QAer.
 - Libraries and librarians may become frustrated too.
 I do not know how to fix these problems, but I would like to raise some
 points.

 The number of patches waiting for QA has decreased. This could be
 explained by the efforts of the QA team, but also by the decrease of SO
 patches - and thus by the decrease of patches going into the QA queue. The
 stack of patches waiting for SO is closed to 200, and my feeling is that
 the amount of weekly SO has never been so low. 2/3 of theses NSO are
 enhancements and 60 have been opened prior to 2013. This bottleneck will
 delay the development of future features.

 One of the more frustrating thing is to see passed QA patches regress to
 the does not apply status, because they have been queuing too long at the
 RM step. It regularly blocks me: I cannot make features for the customers
 when there are too many dependencies waiting to get pushed to the master
 branch.
 Galen, can you explain why there are patches that stay for months in a
 Passed QA status (26 patches are in passed QA since more than one month,
 without any activity)? I really would like to see activity on theses
 patches. I guess it is not always easy to make a decision about some
 patches - invaliding/rejecting them instead of pushing them. But I think it
 is better to go ahead or to reject a patch, rather than blocking it without
 explaining why.
 Does it mean that you would need help? Module maintainers have been
 elected for the 3.16 release: what will be exactly their roles?
 In your 3.14 proposal, you suggest naming master branch committers. Is
 this idea still topical or did you abandon it? I also have the feeling that
 the features have been pushed toward the end of the release cycle. Wouldn't
 it be 

Re: [Koha-devel] [Koha] Summary of Open session at KohaCon13 - with a focus on Funding the Future of Koha.

[Brendan Gallagher]

 I plan to write something, but I need help from a UX person.

 I want a simple taskboard, with bugs, that people can claim by a
 simple click. Then a simple karma type system. ByWater have signed off
 10 Catalyst patches, Catalyst have signed off 5 software.coop and 1
 Bywater patch, leaving Catalyst 4 patches to go ... kind of idea.

 It's not fully formed, but if it sounds like something people would to
 see, or explore further, let me know and I will devote some evenings
 to it.


I would totally be behind an idea like this.

Ideally it would be great to easily see if we (ByWater) really are doing
enough to eventually get our patches signed off.  Something like this would
give us a great snapshot of where we need to quickly pick up the slack or
just help another developer/company.  Although I usually look for patches
that are within my skillset to sign-off on, the company or person that
submitted the patch is never an issue or goal for me to test or sign-off
and I would urge that mind-set stay in the forefront for everyone (which
I'm pretty positive that it will).





 Chris

 --
 Chris Cormack
 Catalyst IT Ltd.
 +64 4 803 2238
 PO Box 11-053, Manners St, Wellington 6142, New Zealand
 ___
 Koha mailing list  http://koha-community.org
 k...@lists.katipo.co.nz
 http://lists.katipo.co.nz/mailman/listinfo/koha




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] New newsletter editor volunteer

[Brendan Gallagher]

Yes Yes - excellent job Daniel!  Can't wait to see you in Argentina ;)

Chad welcome aboard!

Cheers,
-Brendan


On Fri, Sep 13, 2013 at 3:34 PM, Daniel Grobani danielg.k...@gmail.comwrote:

 Hi,

 Chad Roseburg of North Central Regional Library has volunteered to
 assume the role of community newsletter editor starting with the
 December issue. Thanks, Chad!

 As I recall, when I took over from Nicole the only requirement was the
 willingness to do it. What's the current process for Chad to get
 approved by the community?

 Thanks,
 Daniel Grobani
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO

Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: Redding, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Fwd: Canadian Library Association Information Request

[Brendan Gallagher]

Hi Paul -

We also received this (ByWater) - I was traveling list week so I didn't
have time to respond.  I did get an email back today after replying with
the documentation that Robin talks about in here.  I have not had time to
read it yet (other projects first).  Once I read it and respond - I will
also respond here.  (May take me a few days to get to it)

Cheers,
Brendan


On Mon, Apr 29, 2013 at 10:41 AM, Paul Poulain paul.poul...@biblibre.comwrote:

 Hi Koha-devel,

 We recieved through our website the following message. As I suspect
 BibLibre was not the only one to get it, did someone answer ? (and what
 kind of answer) ?


  Message original 
 Sujet: [site biblibre] Canadian Library Association Information Request
 Date : Wed, 17 Apr 2013 15:29:57 +0200
 De : cla.accessibility.proj...@gmail.com
 Pour : commerc...@biblibre.com

 Robin Gallagher a envoyé un message via le formulaire de contact sur
 http://www.biblibre.com/fr/contact.

 Dear BibLibre Representative:

 I am contacting you on behalf of the Canadian Library Association's
 Government Library and Information Management Professionals Network.

 Canadian federal government departments have been ordered to modify their
 websites and web applications to comply with the Web Content Accessibility
 Guidelines (WCAG) 2.0 by July 2013. Within the federal library community,
 there has been some concern about compliance of library management
 systems to
 this standard.

 As a result, the Canadian Library Association (CLA) is conducting a
 survey of
 major vendors of library and information management systems on the
 compliance
 of their products to either the Web Content Accessibility Guidelines
 (version
 2.0) and/or Section 508 of the US Rehabilitation Act, as well as plans
 they
 may have to update their products to comply. The information collected in
 this project will be published to the Network blog and communicated to the
 CLA membership.

 Could you direct me to the member of your organization best suited to
 answer
 a few questions about how your systems meet -- or intend to meet --
 accessibility standards?


 Many thanks,

 Robin Gallagher
 Project Manager, CLA Accessibility  Library Management Systems Project
 Email: cla.accessibility.proj...@gmail.com


 Report as inappropriate:
 http://www.biblibre.com/en/mollom/report/session/1304178e5e9c410b0b


 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: West Haven, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Fwd: Canadian Library Association Information Request

[Brendan Gallagher]

Thanks Ian -

Thanks useful.

-Brendan


On Mon, Apr 29, 2013 at 4:06 PM, Ian Walls koha.sek...@gmail.com wrote:

 You can check Koha against WCAG 2.0 AA using open source AChecker (
 http://AChecker.ca). Last time I ran it, our default template did very
 well. It helps that we're web-based, and our philosophy of not being too
 Javascript dependent pays off here.

 You can also download the Fangs and WebAIM Firefox extensions to check for
 accessibility issues, and see the interface more like a user with assistive
 technologies.

 Cheers,

 Ian
 On Apr 29, 2013 6:42 PM, Brendan Gallagher i...@bywatersolutions.com
 wrote:

 Hi Paul -

 We also received this (ByWater) - I was traveling list week so I didn't
 have time to respond.  I did get an email back today after replying with
 the documentation that Robin talks about in here.  I have not had time to
 read it yet (other projects first).  Once I read it and respond - I will
 also respond here.  (May take me a few days to get to it)

 Cheers,
 Brendan


 On Mon, Apr 29, 2013 at 10:41 AM, Paul Poulain paul.poul...@biblibre.com
  wrote:

 Hi Koha-devel,

 We recieved through our website the following message. As I suspect
 BibLibre was not the only one to get it, did someone answer ? (and what
 kind of answer) ?


  Message original 
 Sujet: [site biblibre] Canadian Library Association Information Request
 Date : Wed, 17 Apr 2013 15:29:57 +0200
 De : cla.accessibility.proj...@gmail.com
 Pour : commerc...@biblibre.com

 Robin Gallagher a envoyé un message via le formulaire de contact sur
 http://www.biblibre.com/fr/contact.

 Dear BibLibre Representative:

 I am contacting you on behalf of the Canadian Library Association's
 Government Library and Information Management Professionals Network.

 Canadian federal government departments have been ordered to modify their
 websites and web applications to comply with the Web Content
 Accessibility
 Guidelines (WCAG) 2.0 by July 2013. Within the federal library community,
 there has been some concern about compliance of library management
 systems to
 this standard.

 As a result, the Canadian Library Association (CLA) is conducting a
 survey of
 major vendors of library and information management systems on the
 compliance
 of their products to either the Web Content Accessibility Guidelines
 (version
 2.0) and/or Section 508 of the US Rehabilitation Act, as well as plans
 they
 may have to update their products to comply. The information collected in
 this project will be published to the Network blog and communicated to
 the
 CLA membership.

 Could you direct me to the member of your organization best suited to
 answer
 a few questions about how your systems meet -- or intend to meet --
 accessibility standards?


 Many thanks,

 Robin Gallagher
 Project Manager, CLA Accessibility  Library Management Systems Project
 Email: cla.accessibility.proj...@gmail.com


 Report as inappropriate:
 http://www.biblibre.com/en/mollom/report/session/1304178e5e9c410b0b


 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




 --

 ---
 Brendan A. Gallagher
 ByWater Solutions
 CEO
 Support and Consulting for Open Source Software
 Installation, Data Migration, Training, Customization, Hosting
 and Complete Support Packages
 Headquarters: Santa Barbara, CA - Office: West Haven, CT
 Phone # (888) 900-8944
 http://bywatersolutions.com
 i...@bywatersolutions.com

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: West Haven, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] My role as QAA

[Brendan Gallagher]

We are all sorry to see you leaving the Koha community.

Just a little follow up we have some great new candidates that we will be
bringing into the Koha community!  Hopefully half as great as you were.
And I think that I will also be offering up my services as a QAA to help
fill in for that absence.

Cheers,
Brendan


On Mon, Feb 25, 2013 at 7:59 AM, Travis Elliott Davis 
elli...@bywatersolutions.com wrote:

 Good morning.

 I recently accepted a job at a local software company, and starting on
 March 18 I will no longer be working full-time on Koha. I would like to
 complete my term as QAA, but I may not have as much time to devote to the
 project and I wanted to make sure there were no objections from the larger
 Koha community. It has been a pleasure working on Koha, and I look forward
 to staying in touch for a long to come even if my job prevents me from
 participating after May.

 Elliott Davis




 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] My changing role...

[Brendan Gallagher]

Hi All -

We are all very sad to see Ruth moving on - but would be very surprised to
see Ruth not kicking around in the Koha IRC channels.  We will all miss
your enthusiasm and excitement about Koha.

As for the translation manager for 3.14 of Koha.  If no one offers to
volunteer for that position.  We at ByWater are willing to host the servers
for that and a few of us here can help be the Admin of that.  I'd love to
see a non-native English speaker volunteer for that position and We
(ByWater) will do everything we can to help pass that responsibility on.
Maybe our new candidates here will be interested in volunteering for this
position.

Cheers,
Brendan


On Mon, Feb 25, 2013 at 8:24 AM, Ruth Bavousett
r...@bywatersolutions.comwrote:


 To my friends in the Koha community,

 I have accepted a position outside the library community, and will be
 leaving ByWater Solutions as of March 8.  It has been an incredible
 almost-five years for me, working on Koha, and getting to meet so many of
 you virtually and in-person.  I say without reservation that some of my
 best friends on the planet are Koha people, some of whom I have never met
 in person.

 I will continue to serve as Translation Manager for the rest of the 3.12
 release cycle; I would like to stay involved in Koha after that, so once I
 see what my workload will look like, I'll decide whether to run for another
 term.  I'll be switching my emails for the lists over to my personal
 account soon, but if you need me for translation matters, email to
 dru...@gmail.com will be your best bet, going forward.

 *D Ruth Bavousett*
 Lead Migration Specialist
 ByWater Solutions
 Support and Consulting for Open Source Software
 Headquarters: Santa Barbara, CA
 Office: Lawrence, KS
 Phone/Fax (888)900-8944
 http://bywatersolutions.com
 r...@bywatersolutions.com

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: West Haven, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] My changing role...

[Brendan Gallagher]

Hi All -

We are all very sad to see Ruth moving on - but would be very surprised to
see Ruth not kicking around in the Koha IRC channels.  We will all miss
your enthusiasm and excitement about Koha.

As for the translation manager for 3.14 of Koha.  If no one offers to
volunteer for that position.  We at ByWater are willing to host the servers
for that and a few of us here can help be the Admin of that.  I'd love to
see a non-native English speaker volunteer for that position and We
(ByWater) will do everything we can to help pass that responsibility on.
Maybe our new candidates here will be interested in volunteering for this
position.

Cheers,
Brendan


On Mon, Feb 25, 2013 at 8:49 AM, Brendan Gallagher 
i...@bywatersolutions.com wrote:

 Hi All -

 We are all very sad to see Ruth moving on - but would be very surprised to
 see Ruth not kicking around in the Koha IRC channels.  We will all miss
 your enthusiasm and excitement about Koha.

 As for the translation manager for 3.14 of Koha.  If no one offers to
 volunteer for that position.  We at ByWater are willing to host the servers
 for that and a few of us here can help be the Admin of that.  I'd love to
 see a non-native English speaker volunteer for that position and We
 (ByWater) will do everything we can to help pass that responsibility on.
 Maybe our new candidates here will be interested in volunteering for this
 position.

 Cheers,
 Brendan


 On Mon, Feb 25, 2013 at 8:24 AM, Ruth Bavousett r...@bywatersolutions.com
  wrote:


 To my friends in the Koha community,

 I have accepted a position outside the library community, and will be
 leaving ByWater Solutions as of March 8.  It has been an incredible
 almost-five years for me, working on Koha, and getting to meet so many of
 you virtually and in-person.  I say without reservation that some of my
 best friends on the planet are Koha people, some of whom I have never met
 in person.

 I will continue to serve as Translation Manager for the rest of the 3.12
 release cycle; I would like to stay involved in Koha after that, so once I
 see what my workload will look like, I'll decide whether to run for another
 term.  I'll be switching my emails for the lists over to my personal
 account soon, but if you need me for translation matters, email to
 dru...@gmail.com will be your best bet, going forward.

 *D Ruth Bavousett*
 Lead Migration Specialist
 ByWater Solutions
 Support and Consulting for Open Source Software
 Headquarters: Santa Barbara, CA
 Office: Lawrence, KS
 Phone/Fax (888)900-8944
 http://bywatersolutions.com
 r...@bywatersolutions.com

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




 --

 ---
 Brendan A. Gallagher
 ByWater Solutions
 CEO

 Support and Consulting for Open Source Software
 Installation, Data Migration, Training, Customization, Hosting
 and Complete Support Packages
 Headquarters: Santa Barbara, CA - Office: West Haven, CT
 Phone # (888) 900-8944
 http://bywatersolutions.com
 i...@bywatersolutions.com




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: West Haven, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] General IRC meeting - 7 February 2013 at 2:00 UTC

[Brendan Gallagher]

Hi All -

I just wanted to point out that there is a general koha IRC meeting coming
today.

http://wiki.koha-community.org/wiki/General_IRC_meeting,_7_February_2013

Thanks,
Brendan

-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Koha hackfest in 2013 in Marseille, (proposing a date)

[Brendan Gallagher]

We'd love to get some tickets soon - as in today or tomorrow - so please
let it be the 18th to the 22nd.

Thanks Brendan


On Mon, Nov 12, 2012 at 9:38 AM, Paul Poulain paul.poul...@free.fr wrote:

 Le 12/11/2012 18:34, Paul Poulain a écrit :
  Hello koha-devel,
 
  As in 2011 and 2012, BibLibre is planning to organize a Koha hackfest
  next year in Marseille.
  Last year, we choose a date where some were not available due to
  important library conferences.
  So, this year, I ask a long time before the date, to be sure there won't
  be any problem:
 
  Is there something that should prevent us from organizing the 3rd
  european Hackfest in Marseille from feb, 18th to feb, 22th ?

 EPIC FAIL: the proposed dates are in *march*, not feb !!!
 from march, 18th to march, 22th

 --
 Paul POULAIN
 http://www.biblibre.com
 Expert en Logiciels Libres pour l'info-doc
 Tel : (33) 4 91 81 35 08
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: West Haven, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Upgrading Koha's license?

[Brendan Gallagher]

+1 for GPL3


On Wed, Nov 14, 2012 at 2:30 PM, Mason James m...@kohaaloha.com wrote:


 On 2012-11-15, at 10:04 AM, Magnus Enger wrote:

  What do we need to do to make inclusion of Bootstrap possible?
 
  Distribute it as GPLv3:
 
  +1 from me, if it means being able to use Bootstrap awesomeness.

 +1 for GPL3


 
  But what do we actually have to do to distribute as GPLv3?

 just update the license headers to GPL3 in the Koha codebase, (a script
 can do this task)


  Do we just have to vote at an IRC meeting,

 yes, or a vote via the Koha mailing-list, or via limesurvey.org

 +1 for an IRC meeting vote


  or would all ~200 developers with code in Koha have to give their
 written consent or something?

 no consent is needed. (consent was already given, when the code was
 released as GPL2+)
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: West Haven, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Bug 8524 Add barcode plugin that does not autofill

[Brendan Gallagher]

No objection here - I tried it out and didn't find a problem.

-Brendan

On Wed, Sep 12, 2012 at 2:30 PM, Chris Cormack ch...@bigballofwax.co.nzwrote:

 Hi All

 I am tempted to push bug 8524
 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8524
 to 3.8.x to be included in 3.8.5

 It is a new plugin that doesn't touch existing code so is safe, and
 actually fixes a 'bug' in certain use cases. Namely if a library
 autobarcodes, but don't barcode their ebooks. (quote 123) :)

 Any objections?

 Chris
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




---
Brendan A. Gallagher
ByWater Solutions
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Proposal for a new coding guideline for command line scripts

[Brendan Gallagher]

+1

Brendan

On Tue, Jul 24, 2012 at 1:09 PM, Chris Cormack ch...@bigballofwax.co.nzwrote:

 +1

 Chris
 On Jul 25, 2012 4:02 AM, Paul Poulain paul.poul...@biblibre.com wrote:

 Hello koha-devel,

 I just pushed a few minuts ago a new script in misc (bug 8376, but it
 doesn't matter for this mail)

 This script has a help that is displayed when you run it with -h. So far
 so good.

 BUT, it has no PODDOC. Not so good.

 I've discovered recently that we could use:
  use Pod::Usage;
 
  sub usage {
  pod2usage( -verbose = 2 );
  exit;
  }
  snip
  usage() if $help;

 That will deal with both POD and -h flag. It's used in some scripts like
 misc/maintenance/touch_all_biblios.pl

 Do we agree it's a good idea to request that for future scripts, and add
 this in the coding guidelines ?

 --
 Paul POULAIN
 http://www.biblibre.com
 Expert en Logiciels Libres pour l'info-doc
 Tel : (33) 4 91 81 35 08
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/


 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
Support and Consulting for Open Source Software
Installation, Data Migration, Training, Customization, Hosting
and Complete Support Packages
Headquarters: Santa Barbara, CA - Office: West Haven, CT
Phone # (888) 900-8944
http://bywatersolutions.com
i...@bywatersolutions.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] About Release process

[Brendan Gallagher]

Hello -

We have recently hired another Developer (Elliot Davis - libsysguy ;) ),
who is charged with creating a more integrated testing suite for ByWater
and getting/challenging some of our partners to complete testing that isn't
automated already or would be difficult to automate.

As for the options...  I totally agree with Colin that the releases are an
Event and should be promoted as an exciting EVENT.  That being said, I
would not want to delay any major new features being put into a new release
no matter the time (we can never really fight the timing of things).  I
think my thought and my response is that We (ByWater at least) need to do
better testing (what does that mean - well we are still working on that).

I think the thing that I struggle with is the definition of a Freeze...
Please speak up and correct me if I am wrong here.  This is what I think it
means currently - if something has an enhancement bug listed (i.e. the idea
is out there before the freeze date) - then it could still be included as
long as the developer gets the code onto the bug report sometime around the
freeze date.  What I think should happen - The code should be pushed to
master before the freeze date - nothing new after the freeze date  (I
hope that makes sense - with what I am trying to explain).  But as others
have said - this is really up to the RM.  Here's a hint - whomever is going
to be the next RM, please include a definition of Freeze for me ;)

Thanks,
Brendan





On Thu, Jul 12, 2012 at 8:43 AM, Colin Campbell 
colin.campb...@ptfs-europe.com wrote:

 On Thu, Jul 12, 2012 at 06:54:36AM -0500, Elliott Davis wrote:
  I think I too side with option 1.
 
 Releases are inherently evil things, (like all deadlines). There is a
 temptation always to pack stuff in there to make a release an event. I
 dont think having beta releases helps ( or skipping .1 releases in
 deployment) because a lot of that testing just does not occur until the
 release goes out into the world no matter how good our intentions are.
 How can we improve things, well any big changes should go into master
 sooner rather than later. The longer big changes are promised the more
 pressure the RM is to ship them. The key task for the RM is really
 deciding what's not yet been proved, and should not make this iteration.
 We do need lots more tests. We rely on far too much untested
 functionality (which may mean we're wrong in our assumptions of what it
 does)
 We have a specific problem that it is much easier to add bits of
 functionality to the system, bits that up the level of entropy in the
 code base, rather than make the strategic changes that build reliability
 into core.
 A specific problem is that we tend to test functionality of an
 enhancement not necessarily how that enhancement integrates with the
 eco-system of Koha and its these kind of conflicts that tend not to
 surface until its been deployed in the real world.
 Colin

 --
 Colin Campbell
 Chief Software Engineer,
 PTFS Europe Limited
 Content Management and Library Solutions
 +44 (0) 800 756 6803 (phone)
 +44 (0) 7759 633626  (mobile)
 colin.campb...@ptfs-europe.com
 skype: colin_campbell2

 http://www.ptfs-europe.com
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/




-- 
---
Brendan A. Gallagher
ByWater Solutions
CEO
Headquarters: Santa Barbara, CA
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/