A new request with request id 8184 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is :
Title : Koha-devel Digest, Vol 200, Issue 24
Category :
Description : 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. Re: Staff interface redesign is ready to be tested
(Katrin Fischer)
2. Debian 9 LTS EOL (dcook@prosentient.com.au)
3. Re: QA for Bug 30988 - Add generic OpenIDConnect client
implementation (dcook@prosentient.com.au)
----------------------------------------------------------------------
Message: 1
Date: Sun, 24 Jul 2022 12:30:30 +0200
From: Katrin Fischer <katrin.fischer.83@web.de>
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Staff interface redesign is ready to be
tested
Message-ID: <547774a5-56ad-92ce-c2ff-6217f6af2cfe@web.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
I still think a dedicated sandbox would be really helpful. What Victor
says is certainly true for smaller patch sets, but this is a big patch
set that touches a lot of files and will conflict very often. So this
could get quite frustrating to set up fast. It would be easier to have a
sandbox 'frozen' with the patch set applied and updated after changes.
Katrin
On 20.07.22 23:57, Victor Grousset/tuxayo wrote:
> On 22-07-08 20:33, Cab Vinton wrote:
>> It's
>> probably a tiny minority of end-users that are used to setting up
>> their own sandboxes from scratch.
>
> Indeed, but with a direct link to
> https://sandbox.bywatersolutions.com/create
> and a few phrases to explain what to fill in the form and then tell to
> wait and refresh until the "Staff" button is visible should be enough
> to make it accessible to most end-users wanting to check it out.
>
> Cheers,
>
------------------------------
Message: 2
Date: Mon, 25 Jul 2022 10:14:26 +1000
From: <dcook@prosentient.com.au>
To: "'Koha Devel'" <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Debian 9 LTS EOL
Message-ID: <055601d89fbb$81a6c280$84f44780$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"
Hi all,
While commenting on Bug 28267, I decided to review what versions of Debian
we support, and I noticed that Debian 9 (Stretch) actually met it's LTS EOL
on 2022-06-30, so it probably makes sense for us to drop support for it at
some point in the near future too.
Debian 10 (Buster) will be regular EOL in the next couple of months, and
then it will get a LTS period of another couple extra years. (Interesting to
note that Debian LTS isn't actually handled by the Debian Security team but
rather a separate group of volunteers.)
It looks like Ubuntu 18.04 will end its "standard support" in April 2023, so
we nearly have 1 more year on it.
It looks like Debian 9 (Stretch) and Ubuntu 18.04 (Bionic) both have MariaDB
10.1.x, so I suppose we can't drop support for that DB version until both
OSes are no longer supported.
https://wiki.koha-community.org/wiki/System_requirements_and_recommendations
https://wiki.debian.org/LTS
https://wiki.debian.org/DebianReleases
https://wiki.ubuntu.com/Releases
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/20220725/09731de5/attachment-0001.htm>
------------------------------
Message: 3
Date: Mon, 25 Jul 2022 11:27:24 +1000
From: <dcook@prosentient.com.au>
To: "'Tomas Cohen Arazi'" <tomascohen@gmail.com>, "'Martin Renvoize'"
<martin.renvoize@ptfs-europe.com>
Cc: "'Koha Devel'" <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] QA for Bug 30988 - Add generic OpenIDConnect
client implementation
Message-ID: <055e01d89fc5$c49f2f50$4ddd8df0$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"
Hi Tomas,
I thought that you were working on an OpenID Connect implementation, but then I started to doubt my memory. I suppose the takeaway is that I should never doubt myself haha.
Yeah Bug 30988 is basically a copy of Bug 10988 (the Google version). I have never liked Bug 10988, but it’s hard to argue with something in production, and I’m tired of maintaining my own local OpenID Connect implementation these last 8 years.
Of course, there are times where I think about writing a Koha plugin to do it instead. Locally, I’ve implemented it as a sort of built-in plugin using these hooks https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24539. Those hooks could always be changed to support the Koha Plugin system though.
Anyway, please CC me into your implementation when you submit it.
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: Tomas Cohen Arazi <tomascohen@gmail.com>
Sent: Sunday, 24 July 2022 4:47 AM
To: David Cook <dcook@prosentient.com.au>
Cc: Koha Devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] QA for Bug 30988 - Add generic OpenIDConnect client implementation
Hi, David. I meant to answer your first email. I'm submitting (immediately) an alternative implementation I've been working on but failed to wrap up sooner.
I've read the one you pointed and if fairly similar to the google oaidc implementation for OPAC, so it is correct.
My plan is to do it for staff as well, using libraries.
El vie, 22 jul 2022 7:03, <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > escribió:
Hi all,
Just wondering if anyone has time to QA “Bug 30988 - Add generic OpenIDConnect client implementation”. It would be great to get this additional authentication option into Koha as it would really round out Koha’s AuthN offerings.
I could do some testing for bugs of the QAer’s choice if that helps.
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
_______________________________________________
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/20220725/34e2dd7e/attachment-0001.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 200, Issue 24
*******************************************
NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.