<!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 14615 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 192, Issue 1<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. Re: More handy fixes in Zebra 2.2.3 (Victor Grousset/tuxayo)<br> 2. Translation: One week remaining to complete 21.05 translation<br> to avoid some duplicate work when 21.11 will be out<br> (Victor Grousset/tuxayo)<br> 3. Re: Replacement of mailman (mailing lists)<br> (dcook@prosentient.com.au)<br> 4. Re: Replacement of mailman (mailing lists) (Fridolin SOMERS)<br> 5. Re: Koha 20.05.17 released (Michael Kuhn)<br> 6. custom core patches management (David Schmidt)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 1 Nov 2021 21:54:58 +0100<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: dcook@prosentient.com.au, 'koha-devel'<br> <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] More handy fixes in Zebra 2.2.3<br>Message-ID: <95f99978-69c9-c6ae-2bcf-68f3d72bea83@tuxayo.net><br>Content-Type: text/plain; charset=windows-1252; format=flowed<br><br>good news, thanks for the bug reports :D<br><br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 2 Nov 2021 04:43:37 +0100<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: koha-translate@lists.koha-community.org, koha-devel<br> <koha-devel@lists.koha-community.org>, Koha <Koha@lists.katipo.co.nz><br>Cc: gt traduction kohala <gt_traduction_kohala@framalistes.org><br>Subject: [Koha-devel] Translation: One week remaining to complete<br> 21.05 translation to avoid some duplicate work when 21.11 will be out<br>Message-ID: <ea24f5df-6149-a7a1-03ee-c7175cfa23fb@tuxayo.net><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hi :)<br><br>If your languages of choices don't have yet a full translation for Koha <br>21.05, it's a good time to put as much a possible work towards that.<br><br>Because in a week, the 10th will be the string freeze to prepare the <br>major release of Koha 21.11 which the scheduled around the 26th.<br>At that moment, translation of 21.05 will be copied as a starting point <br>for 21.11.<br>After that, any translation work on 21.05 will have to be copied to 21.11.<br>If you usually translate multiple versions, that will spare you one copy <br>compared if you do it after the 10th.<br>If you usually only translate the latest version, it will still help <br>people that will stay on 21.05 to benefit from your work.<br><br>↓↓↓↓↓↓↓↓↓↓↓<br>https://translate.koha-community.org/projects/21.05/<br>↑↑↑↑↑↑↑↑↑↑↑<br><br>Happy translating :)<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 3<br>Date: Tue, 2 Nov 2021 17:09:58 +1100<br>From: <dcook@prosentient.com.au><br>To: "'Renvoize, Martin'" <martin.renvoize@ptfs-europe.com>, "'Koha<br> Devel'" <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Replacement of mailman (mailing lists)<br>Message-ID: <0d3b01d7cfb0$439a0500$cace0f00$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Did we have any further discussion about Discourse?<br><br> <br><br>I’ve decided to use it for a different project, so I’ve looked at setting it up today. The installation instructions aren’t perfect, so I had to do some of my own troubleshooting, and they use custom scripts to orchestrate instead of using Docker Compose which makes me a bit uncomfortable (see https://meta.discourse.org/t/community-supported-official-docker-image/83768/18), but overall it went fairly smoothly. <br><br> <br><br>Actually going to be looking at migrating an old listserv over to it, so I can probably give more details as I do that. <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 Renvoize, Martin<br>Sent: Saturday, 2 October 2021 4:28 PM<br>To: Koha Devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Replacement of mailman (mailing lists)<br><br> <br><br>Discourse sounds good to me too.. something to work on next cycle?<br><br> <br><br>Do we have a host in mind?<br><br> <br><br>On Fri, 20 Aug 2021, 12:47 am Victor Grousset/tuxayo, <victor@tuxayo.net <mailto:victor@tuxayo.net> > wrote:<br><br>On 21-08-19 08:42, dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> wrote:<br>> It does seem like Discourse is reasonably popular although I’ve only <br>> engaged with it from the forum perspective. It looks like it does have <br>> mailing list support but I don’t know what that means exactly.<br><br><br>https://meta.discourse.org/t/what-is-mailing-list-mode/46008<br> > In mailing list mode you will receive one email per post, as happens <br>with traditional mailing lists. This is desirable if you prefer to <br>interact via email, without visiting the forum website.<br><br>https://meta.discourse.org/t/what-is-mailing-list-mode/46008/10<br> > Yes, provided you configure “email reply support” appropriately<br><br><br>I just checked on an instance and it's possible to watch a category. It <br>would have the same effect as subscribing to a mailing list.<br><br>---<br><br>Also, it's possible if it's worth the work to import a mailing list.<br>https://meta.discourse.org/t/discourse-vs-email-mailing-lists/54298/1<br><br>see<br>=> How do I import my mailing list?<br><br>=> My organisation manages multiple mailing lists. Can they be imported <br>incrementally?<br><br><br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org <mailto: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/20211102/36318851/attachment-0001.htm><br><br>------------------------------<br><br>Message: 4<br>Date: Mon, 1 Nov 2021 20:48:49 -1000<br>From: Fridolin SOMERS <fridolin.somers@biblibre.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Replacement of mailman (mailing lists)<br>Message-ID: <ef27bd5c-bb72-dfb5-e576-54a6c184fa91@biblibre.com><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Sure, sounds great.<br>I know it from LXD https://discuss.linuxcontainers.org/<br><br>This can be a topic for next cycle.<br><br>Best regards,<br><br>Le 01/11/2021 à 20:09, dcook@prosentient.com.au a écrit :<br>> Did we have any further discussion about Discourse?<br>> <br>> I’ve decided to use it for a different project, so I’ve looked at <br>> setting it up today. The installation instructions aren’t perfect, so I <br>> had to do some of my own troubleshooting, and they use custom scripts to <br>> orchestrate instead of using Docker Compose which makes me a bit <br>> uncomfortable (see <br>> https://meta.discourse.org/t/community-supported-official-docker-image/83768/18 <br>> <https://meta.discourse.org/t/community-supported-official-docker-image/83768/18>), <br>> but overall it went fairly smoothly.<br>> <br>> Actually going to be looking at migrating an old listserv over to it, so <br>> I can probably give more details as I do that.<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>> Office: 02 9212 0899<br>> <br>> Online: 02 8005 0595<br>> <br>> *From:*Koha-devel <koha-devel-bounces@lists.koha-community.org> *On <br>> Behalf Of *Renvoize, Martin<br>> *Sent:* Saturday, 2 October 2021 4:28 PM<br>> *To:* Koha Devel <koha-devel@lists.koha-community.org><br>> *Subject:* Re: [Koha-devel] Replacement of mailman (mailing lists)<br>> <br>> Discourse sounds good to me too.. something to work on next cycle?<br>> <br>> Do we have a host in mind?<br>> <br>> On Fri, 20 Aug 2021, 12:47 am Victor Grousset/tuxayo, <victor@tuxayo.net <br>> <mailto:victor@tuxayo.net>> wrote:<br>> <br>> On 21-08-19 08:42, dcook@prosentient.com.au<br>> <mailto:dcook@prosentient.com.au> wrote:<br>> > It does seem like Discourse is reasonably popular although I’ve only<br>> > engaged with it from the forum perspective. It looks like it does<br>> have<br>> > mailing list support but I don’t know what that means exactly.<br>> <br>> <br>> https://meta.discourse.org/t/what-is-mailing-list-mode/46008<br>> <https://meta.discourse.org/t/what-is-mailing-list-mode/46008><br>> > In mailing list mode you will receive one email per post, as<br>> happens<br>> with traditional mailing lists. This is desirable if you prefer to<br>> interact via email, without visiting the forum website.<br>> <br>> https://meta.discourse.org/t/what-is-mailing-list-mode/46008/10<br>> <https://meta.discourse.org/t/what-is-mailing-list-mode/46008/10><br>> > Yes, provided you configure “email reply support” appropriately<br>> <br>> <br>> I just checked on an instance and it's possible to watch a category. It<br>> would have the same effect as subscribing to a mailing list.<br>> <br>> ---<br>> <br>> Also, it's possible if it's worth the work to import a mailing list.<br>> https://meta.discourse.org/t/discourse-vs-email-mailing-lists/54298/1 <https://meta.discourse.org/t/discourse-vs-email-mailing-lists/54298/1><br>> <br>> see<br>> => How do I import my mailing list?<br>> <br>> => My organisation manages multiple mailing lists. Can they be imported<br>> incrementally?<br>> <br>> <br>> <br>> Cheers,<br>> <br>> -- <br>> Victor Grousset/tuxayo<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> <mailto:Koha-devel@lists.koha-community.org><br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel><br>> website : https://www.koha-community.org/<br>> <https://www.koha-community.org/><br>> git : https://git.koha-community.org/ <https://git.koha-community.org/><br>> bugs : https://bugs.koha-community.org/<br>> <https://bugs.koha-community.org/><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>Fridolin SOMERS <fridolin.somers@biblibre.com><br>Software and system maintainer 🦄<br>BibLibre, France<br><br><br>------------------------------<br><br>Message: 5<br>Date: Tue, 2 Nov 2021 09:42:07 +0100<br>From: Michael Kuhn <mik@adminkuhn.ch><br>To: koha-devel@lists.koha-community.org, Victor Grousset/tuxayo<br> <victor@tuxayo.net><br>Subject: Re: [Koha-devel] Koha 20.05.17 released<br>Message-ID: <cc260c01-8932-898b-bf6d-63f392f1c427@adminkuhn.ch><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hi Victor<br><br> > The Koha Community is happy to announce the release of Koha 20.05.17<br> ><br> > The full release notes can be found at:<br> > https://koha-community.org/koha-20-05-17-released/<br><br>This URL does not lead to the release notes. Can you please give us the <br>correct URL?<br><br>Best wishes: Michael<br>-- <br>Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis<br>Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz<br>T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch<br><br><br>------------------------------<br><br>Message: 6<br>Date: Tue, 02 Nov 2021 11:00:56 +0100<br>From: "David Schmidt" <mail@davidschmidt.at><br>To: Koha-devel@lists.koha-community.org<br>Subject: [Koha-devel] custom core patches management<br>Message-ID: <ca9f92c8-d787-49ab-a3b4-725642a46253@www.fastmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hello koha community,<br><br>We made some changes to our Koha instance and are now looking for a mechanism to apply them to a new installation.<br><br>- some of the changes are simply new files, thats easy.<br>- some changes were possible to put into plugins or use existing hooks.<br><br>but how do you deal with changes to the koha sourcecode?<br><br>this is our strategy:<br><br>1) we have a git repo with our koha source code.<br>2) if we change code in Foobar.pm we create 3 files.<br>Foobar.pm.orig<br>Foobar.pm.changed<br>Foobar.pm.patch<br>3) on a new koha instance next we have a script `install.sh` that compares Foobar.pm.orig with the installed file. if they match, the patch is applied.<br><br>Does that sound like a good idea?<br>How do YOU manage core changes that do not go upstream?<br><br>cheers,<br>david<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211102/dc28603c/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 192, Issue 1<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>