<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 6307 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 204, Issue 4<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. New pushes, new KTD images (Tomas Cohen Arazi)<br> 2. ERM - workflow change (Tomas Cohen Arazi)<br> 3. Re: OIDC client pushed to master! (Tomas Cohen Arazi)<br> 4. Re: ERM - workflow change (Renvoize, Martin)<br> 5. Re: ERM - workflow change (David Cook)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 9 Nov 2022 09:42:37 -0300<br>From: Tomas Cohen Arazi <tomascohen@gmail.com><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] New pushes, new KTD images<br>Message-ID:<br> <CABZfb=Vf1U4v94Xq0QZB=hHANnHpgci8dF4zA81trymmid9ZPA@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all, both ERM and the OIDC/OAuth2 integration have been pushed. As some<br>of you noted, they have new dependencies. New KTD images have been built<br>before pushing to avoid issues, so please do the usual so things keep<br>working:<br><br>$ ktd pull<br><br>Best regards<br><br>PS: If you use other ktd flags, you can also pull like:<br><br>$ ktd --selenium --es7 --sso pull<br><br>-- <br>Tomás Cohen Arazi<br>Theke Solutions (http://theke.io)<br>✆ +54 9351 3513384<br>GPG: B2F3C15F<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221109/840e0c5a/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 9 Nov 2022 12:53:49 -0300<br>From: Tomas Cohen Arazi <tomascohen@gmail.com><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] ERM - workflow change<br>Message-ID:<br> <CABZfb=Wn5xjvZ4rOuSYsaEzsz8XX-aOLwxz-41aRhUWD2WEMAg@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all, we pushed ERM but didn't communicate some decisions made:<br><br>- For running the ERM component (and in the future any other Vue-driven<br>thing) a build step needs to happen. Either:<br><br>$ yarn build_js<br><br>or (the dev-oriented version):<br><br>$ yarn watch_js<br><br>- We could've gone 'the SCSS' way, in which the RM(aint) compiles the thing<br>and pushes to Git along with the changes. But we decided it would have an<br>impact on the size of the repository pretty fast. So for now, the decision<br>is we will do it at release time. This is also common practice on Vue<br>projects.<br><br>- We could add the build as part of the 'reset_all' command KTD users are<br>familiar with. TBD<br><br>- Yes, now that running Koha requires a build step, we could just add SCSS<br>there, that's to be discussed early next cycle.<br><br>- We need a way to pre-bundle all the dependencies in KTD, so people can<br>fire up KTD while being offline. Agustín is wrapping up a proposal for<br>this. TBD<br><br>Please share your thoughts, and sorry for not communicating this earlier.<br><br>-- <br>Tomás Cohen Arazi<br>Theke Solutions (http://theke.io)<br>✆ +54 9351 3513384<br>GPG: B2F3C15F<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221109/973145bb/attachment-0001.htm><br><br>------------------------------<br><br>Message: 3<br>Date: Wed, 9 Nov 2022 13:32:08 -0300<br>From: Tomas Cohen Arazi <tomascohen@gmail.com><br>To: David Cook <dcook@prosentient.com.au><br>Cc: koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] OIDC client pushed to master!<br>Message-ID:<br> <CABZfb=U0jV==mx3qv=i8AGO0rTJvpdXN-m5ZtpjYYTFSqiB7Ew@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Thank you David for all your valuable input. Looking forward to those<br>follow-ups.<br><br>El mar, 8 nov 2022 a las 23:36, David Cook (<dcook@prosentient.com.au>)<br>escribió:<br><br>> I was pumped to see this morning that the OIDC client was pushed to master!<br>><br>><br>><br>> I have 2 very easy follow-ups that I think are necessary before the<br>> feature is prod ready, so if someone could take a look at those, that would<br>> be awesome.<br>><br>><br>><br>> Bug 32138 - OIDC client uses backwards default mapping<br>><br>> Bug 32139 - "Update on login" setting not set when creating domain from<br>> new IdP page<br>><br>><br>><br>> A nice to have would also be the following although not necessary from a<br>> functionality point of view:<br>><br>> Bug 32141 - New and Edit Identity Provider UIs inconsistent<br>><br>><br>><br>> Thanks!<br>><br>><br>><br>> David Cook<br>><br>> Senior Software Engineer<br>><br>> Prosentient Systems<br>><br>> Suite 7.03<br>><br>> 6a Glen St<br>><br>> Milsons Point NSW 2061<br>><br>> Australia<br>><br>><br>><br>> Office: 02 9212 0899<br>><br>> Online: 02 8005 0595<br>><br>><br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br><br><br>-- <br>Tomás Cohen Arazi<br>Theke Solutions (http://theke.io)<br>✆ +54 9351 3513384<br>GPG: B2F3C15F<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221109/3dbcf76f/attachment-0001.htm><br><br>------------------------------<br><br>Message: 4<br>Date: Wed, 9 Nov 2022 17:33:30 +0000<br>From: "Renvoize, Martin" <martin.renvoize@ptfs-europe.com><br>To: Koha Devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] ERM - workflow change<br>Message-ID:<br> <CAB7SL8DLU-kOp9EYDhWCWUwT+csR12XR28eciizhY7G4G5LWmw@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>To get up and running fast in k-t-d,<br><br>kshell<br>$ kshell<br>k$ yarn install<br>k$ yarn build_js<br><br><br><br>On Wed, 9 Nov 2022, 3:54 pm Tomas Cohen Arazi, <tomascohen@gmail.com> wrote:<br><br>> Hi all, we pushed ERM but didn't communicate some decisions made:<br>><br>> - For running the ERM component (and in the future any other Vue-driven<br>> thing) a build step needs to happen. Either:<br>><br>> $ yarn build_js<br>><br>> or (the dev-oriented version):<br>><br>> $ yarn watch_js<br>><br>> - We could've gone 'the SCSS' way, in which the RM(aint) compiles the<br>> thing and pushes to Git along with the changes. But we decided it would<br>> have an impact on the size of the repository pretty fast. So for now, the<br>> decision is we will do it at release time. This is also common practice on<br>> Vue projects.<br>><br>> - We could add the build as part of the 'reset_all' command KTD users are<br>> familiar with. TBD<br>><br>> - Yes, now that running Koha requires a build step, we could just add SCSS<br>> there, that's to be discussed early next cycle.<br>><br>> - We need a way to pre-bundle all the dependencies in KTD, so people can<br>> fire up KTD while being offline. Agustín is wrapping up a proposal for<br>> this. TBD<br>><br>> Please share your thoughts, and sorry for not communicating this earlier.<br>><br>> --<br>> Tomás Cohen Arazi<br>> Theke Solutions (http://theke.io)<br>> ✆ +54 9351 3513384<br>> GPG: B2F3C15F<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221109/10c7835e/attachment-0001.htm><br><br>------------------------------<br><br>Message: 5<br>Date: Thu, 10 Nov 2022 09:28:00 +1100<br>From: "David Cook" <dcook@prosentient.com.au><br>To: "'Tomas Cohen Arazi'" <tomascohen@gmail.com>, "'koha-devel'"<br> <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] ERM - workflow change<br>Message-ID: <044a01d8f48a$8779cbc0$966d6340$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>I’ll have to think more about it and have a play…<br><br> <br><br>In terms of regular koha-testing-docker dev/test usage, I think that you’d only need to build once in a while (unless you’re changing ERM code)? So I’m not too worried about this.<br><br> <br><br>But how does the yarn build factor into building Koha packages? Do we need to add the yarn build to the debian/rules file? Or would we change “debian/build-git-snapshot” to unpack the “git archive”, do the yarn build, and then re-package and pass to pdebuild?<br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Tomas Cohen Arazi<br>Sent: Thursday, 10 November 2022 2:54 AM<br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] ERM - workflow change<br><br> <br><br>Hi all, we pushed ERM but didn't communicate some decisions made:<br><br> <br><br>- For running the ERM component (and in the future any other Vue-driven thing) a build step needs to happen. Either:<br><br> <br><br>$ yarn build_js<br><br> <br><br>or (the dev-oriented version):<br><br> <br><br>$ yarn watch_js<br><br> <br><br>- We could've gone 'the SCSS' way, in which the RM(aint) compiles the thing and pushes to Git along with the changes. But we decided it would have an impact on the size of the repository pretty fast. So for now, the decision is we will do it at release time. This is also common practice on Vue projects.<br><br> <br><br>- We could add the build as part of the 'reset_all' command KTD users are familiar with. TBD<br><br> <br><br>- Yes, now that running Koha requires a build step, we could just add SCSS there, that's to be discussed early next cycle.<br><br> <br><br>- We need a way to pre-bundle all the dependencies in KTD, so people can fire up KTD while being offline. Agustín is wrapping up a proposal for this. TBD<br><br><br> <br><br>Please share your thoughts, and sorry for not communicating this earlier.<br><br> <br><br>-- <br><br>Tomás Cohen Arazi<br><br>Theke Solutions (http://theke.io <http://theke.io/> )<br>✆ +54 9351 3513384<br>GPG: B2F3C15F<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221110/e540fc42/attachment.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 204, Issue 4<br>******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>