Send Koha-devel mailing list submissions to
    koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
    koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
    koha-devel-owner@lists.koha-community.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."


Today's Topics:

1. Automatic graceful reloading of Koha after plugin
install/upgrade (dcook@prosentient.com.au)
2. Re: Gitlab policy changes (dcook@prosentient.com.au)
3. Developing/Testing Zebra using Docker (dcook@prosentient.com.au)


----------------------------------------------------------------------

Message: 1
Date: Thu, 26 May 2022 10:39:58 +1000
From: <dcook@prosentient.com.au>
To: "'koha-devel'" <koha-devel@lists.koha-community.org>
Cc: "'Kyle Hall'" <kyle@bywatersolutions.com>
Subject: [Koha-devel] Automatic graceful reloading of Koha after
    plugin install/upgrade
Message-ID: <0b5c01d87099$2952a960$7bf7fc20$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"

Hi all,



How good would it be to have automatic graceful reloading of Koha after
plugin install/upgrade?



Andreas Jonsson suggested it at
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21366#c8 and it
looks like it's easily doable using a SIGHUP as a web user. (Admittedly,
I've just sent the SIGUP as the relevant CLI user, but it should be fine as
a web user as well.)



Having to manually restart Koha after a plugin install/upgrade is rather
annoying and even impossible for some libraries, so it seems like this would
be a big improvement.



Thoughts?



David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia



Office: 02 9212 0899

Online: 02 8005 0595



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220526/c226cbca/attachment-0001.htm>

------------------------------

Message: 2
Date: Thu, 26 May 2022 10:54:01 +1000
From: <dcook@prosentient.com.au>
To: "'Doug Kingston'" <dpk@randomnotes.org>, "'Tomas Cohen Arazi'"
    <tomascohen@gmail.com>, "'Chris Cormack'" <chrisc@catalyst.net.nz>
Cc: "'koha-devel'" <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Gitlab policy changes
Message-ID: <0b6101d8709b$1ea3c240$5beb46c0$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"

Does The Horowhenua Library Trust still exist? It looks like it was dissolved by their local council back in 2016. I tried to find some recent information on it, but I could only see https://www.stuff.co.nz/dominion-post/news/local-papers/horowhenua-mail/80627473/trust-running-horowhenua-libraries-and-te-takere-to-be-axed-in-a-month



https://fyi.org.nz/request/4270-dissolution-of-te-horowhenua-trust

https://www.tetakere.org.nz/About-Us/Our-Story



Looks like the Koha trademark in NZ is marked as owned by “Te Horowhenua Trust 2016” (case no 953837).



Ah Joann already covered this in https://wiki.koha-community.org/wiki/THT_and_Koha. While all the details aren’t there, it looks like a new trust must’ve been created.



I imagine the Koha folk in NZ might have more information?



David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia



Office: 02 9212 0899

Online: 02 8005 0595



From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Doug Kingston
Sent: Thursday, 26 May 2022 10:26 AM
To: Tomas Cohen Arazi <tomascohen@gmail.com>
Cc: koha-devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Gitlab policy changes



I believe that The Horowhenua Library Trust as the non-profit behind koha-community.org <http://koha-community.org> and trustees of the koha codebase would qualify to enroll as an open-source organization.



-Doug-



On Wed, May 25, 2022 at 5:06 PM Tomas Cohen Arazi <tomascohen@gmail.com <mailto:tomascohen@gmail.com> > wrote:

Most limitations are about workers quotas. We can still rely on their services and run our own workers? It feels we should try enrolling as an open source organization, it at least see where the process takes us.



Worth hearing all opinions!



El mié, 25 may 2022 20:55, <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > escribió:

Where did you see that quote, Jonathan?

Here’s the relevant two lines I’m seeing:
1. “Not seeking profit: Your organization must not seek to make a profit through services or by charging for higher tiers. Accepting donations to sustain your efforts is ok. Read more about this requirement here.”
2. “Not seek profit: An organization can accept donations to sustain its work, but it can’t seek to make a profit by selling services, by charging for enhancements or add-ons, or by other means."

In theory, the organisation should be the Koha Community so it might be OK, since it doesn't sell services. That's in contrast to Duraspace/Lyrasis which is the non-profit company that develops DSpace and hosts a lot of its infrastructure; they sell DSpace services. I suppose though only Gitlab can ultimately make that call though?

--

That said, overall, I don't know that we need to apply to the Gitlab for Open Source Program though? It might have some benefits but it might be relying too much on a third-party that can change its services on a whim?

David Cook
Senior Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia

Office: 02 9212 0899
Online: 02 8005 0595

From: Koha-devel <koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org> > On Behalf Of Jonathan Druart
Sent: Thursday, 26 May 2022 8:33 AM
To: Tomas Cohen Arazi <tomascohen@gmail.com <mailto:tomascohen@gmail.com> >
Cc: koha-devel <koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> >
Subject: Re: [Koha-devel] Gitlab policy changes

I had a look at it a couple of months ago but at some point you have to "certify that project maintainer are not seeking profit from this project by, for example, selling services"...
Le mer. 25 mai 2022 à 17:51, Tomas Cohen Arazi <mailto:tomascohen@gmail.com <mailto:tomascohen@gmail.com> > a écrit :
Hi, we need to take a look at the upcoming changes and make a decision on enrolling as an Open Source project:

https://about.gitlab.com/blog/2022/02/04/ultimate-perks-for-open-source-projects/

Please read carefully so we can make a decision eventually.

--
Tomás Cohen Arazi
Theke Solutions (http://theke.io/)
✆ +54 9351 3513384
GPG: B2F3C15F
_______________________________________________
Koha-devel mailing list
mailto:Koha-devel@lists.koha-community.org <mailto: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/

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org <mailto: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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220526/1d9f0ee7/attachment-0001.htm>

------------------------------

Message: 3
Date: Thu, 26 May 2022 12:07:53 +1000
From: <dcook@prosentient.com.au>
To: "'koha-devel'" <koha-devel@lists.koha-community.org>
Cc: "'Fridolin SOMERS'" <fridolin.somers@biblibre.com>, "'Tomas Cohen
    Arazi'" <tomascohen@theke.io>, "'Martin Renvoize'"
    <martin.renvoize@ptfs-europe.com>
Subject: [Koha-devel] Developing/Testing Zebra using Docker
Message-ID: <0b8901d870a5$75840250$608c06f0$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"

Hi nerds,



Ever feel like Zebra is an intimidating black box of mystery? Well, you're
certainly not alone. That's how I felt when I first encountered it over 10
years ago.



Over the past decade, I've read through the C code and submitted issue
reports to Indexdata, but it wasn't until the other day that I decided I'd
try hacking on Zebra to try to understand its operation better (especially
faceting).



I kept notes of my process for developing and testing Zebra and I've posted
them to https://wiki.koha-community.org/wiki/Developing_Zebra. Using these
straightforward steps you should be able to hack, compile, and run Zebra.
(At some stage, I might actually provide a Dockerfile or Docker image that
is even more convenient.)



When looking at faceting, I wasn't able to solve the problem, but I was able
to isolate the problematic function by hacking on Zebra, and now I'm waiting
to hear back from Indexdata for advice. So I think it was a useful exercise.



I think Tomas has already hacked on Zebra, so he probably doesn't need this,
but I thought it might be interesting for people to review and try if they
were interested.



David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia



Office: 02 9212 0899

Online: 02 8005 0595



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220526/38fb1652/attachment.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
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/


------------------------------

End of Koha-devel Digest, Vol 198, Issue 20
*******************************************