Re: [Koha-devel] Growing size of koha/koha-testing:master
On 24-02-04 23:30, David Cook via Koha-devel wrote: Do we know what’s contributing to this? After running `ncdu /` from inside KTD Debian 10 (the smallest image it seems) - 661 M /kohadevbox/Cypress - 347 M /kohadevbox/node_modules - 95 M /kohadevbox/misc4dev - 224 M /usr/lib/locale (does locales are needed for Koha? because all are generated) - 410 M /usr/lib/x86_64-linux-gnu , various lib, maybe libLLVM and guile are not needed - 93 M /usr/lib/gcc - 270 M /usr/share/locale & /usr/share/doc not sure that prunable depending on how packages are made in Debian. Maybe part can be pruned via a dirty rm -rf like it seems to be done for the apt repo metadata in dockerfiles. Seen that a few times. - 400 M /usr/local/share/.cache/yarn likely everything is needed to be able to rebuild CSS & vue without having to redownload. Which is done on start so not only needed when working with UI. Ok maybe some stuff is not needed? Same questions with /kohadevbox/node_modules npm(node) and yarn have redundancy in their cache >_< They share all of their top 10 packages (some with same size, other with quite different) ^^" I guess one is used for SCSS compilation and another one for vue and cypress. But they still have in common the packages of the 3, hmm Cheers, -- Victor Grousset/tuxayo ___ 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] Anybody still using tarballs?
On 23-11-10 08:50, Jonathan Druart wrote: You missed the original request, Victor. The .po files will be missing from the src and so the git extract won't be enough. Indeed! Read it and forgot it when looking at how to get them from the forge... > I think we better need to have a job triggered on tags pushed that will build and push the .tar.gz files. If there isn't much usage maybe it's ok to have one tarball for Koha itself and one for the .po files. And if there are requests for a complete tarball then maybe do a job. Not sure about the tarball usage but if it's for manual installs then having a step to extract the .po tarball in the directory of koha could be okay for users. Cheers, -- Victor Grousset/tuxayo ___ 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] Anybody still using tarballs?
Hi :) To still provide tarballs without release process steps to maintain and perform every time there is still this: https://git.koha-community.org/Koha-community/Koha/tags No files for signature though. Though, where can people find the rmaint public keys anyway? So I'm not sure anyone uses this to get Koha. Hum, after trying, the forge is a bit weird about the tarball feature, it seems the link doesn't work. But after like 30 sec of processing it works. (might need to click again) And subsequent clicks work directly. Direct link still work though: https://git.koha-community.org/Koha-community/Koha/archive/v23.05.05.tar.gz Oh no when using the direct link the 1st time, it ends up in a 500 error and next try it works. (timeout?) So having the release process get the tarball URL to trigger the generation would work. Still a bit wack but could be an alternative to keep tarballs without much work. (same behavior on Forgejo, tested on codeberg.org but it's likely with a fast enough server the request doesn't timeout or something) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Need to complete coding guidelines about when to use SQL and where.
Hi :) We need some additions/changes to the SQL 8 guideline https://wiki.koha-community.org/wiki/Coding_Guidelines#SQL8:_SQL_code_in_.pl_scripts Like it allows implicitly SQL in .pm doesn't mention DBIC. In last meeting there was a discussion are here are some takeaways (https://ilbot3.kohaaloha.com/koha/2023-01-11#i_2343089) Add in the guidelines: No SQL by default in any place (in new code) except for database upgrades. But if it's not possible to do a query with the ORM or if it's much less readable or a performance bottleneck, then it should be done in a custom subroutine in the relevant DBIC schema class.[1][2] If SQL needed: SQL::Abstract syntax should be used over raw SQL in the /Koha namespace.[3] Syntax: https://metacpan.org/pod/SQL::Abstract::Classic#WHERE-CLAUSES What about command-line scripts? Should new ones/major changes use the ORM by default? Is that easy to access it from a script? SQL8: "SQL is also tolerated for reports" even new report? (assuming that still happens) [1] need more feedback on that last part. [2] Is DBIC schema class the right term? [3] why not everywhere? (except db upgrades) related to the upcoming question about scrips -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Next dev meeting 25 January: errata on hours
I confused UTC with my local time! :o So it's this: Australia/Sydney Thu Jan 26 10:00:00 2023 AEDT NZThu Jan 26 12:00:00 2023 NZDT Pacific/TahitiWed Jan 25 13:00:00 2023 -10 America/Los_Angeles Wed Jan 25 15:00:00 2023 PST US/CentralWed Jan 25 17:00:00 2023 CST America/Lima Wed Jan 25 18:00:00 2023 -05 America/New_York Wed Jan 25 18:00:00 2023 EST UTC Wed Jan 25 23:00:00 2023 UTC -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Trouble for the Gitea project: forked to Forgejo
Hi :) Thanks David Nind for sharing this info on the last dev meeting: Use of Gitea: We use Gitea for git.koha-community.org. Gitea was "forked" and is now Forgejo[1] - see the links update and related links[2] (sounds eerily familiar 8-(.. ). The community needs to look at what to do next, such as whether to continue to use Gitea, update to Forgejo, do something else (David Nind) [1] https://forgejo.org/ > [2] https://forgejo.org/2022-12-26-monthly-update Comments during the meeting: forgejo is the 'good' one? that's what it looks like ^^ "After Gitea Ltd confirmed the takeover of the Gitea project on 30 October 2022, a group of people proposed that Codeberg e.V. should become the custodian of a fork of Gitea. The proposal was accepted 16 November 2022" - e.V. is a German thing actually More details: e. V. is the legal form for associations in Germany and Codeberg e. V. is known for their Gitea (well, now Forgejo) instance that became host to a decent number of libre projects in the last two years. (likely they moved away from GitHub and not wanted the not libre GitLab instance at GitLab.com (open-core)) Trivia: > Forgejo (pronounced /forˈd͡ʒe.jo/) is inspired by forĝejo, the Esperanto word for forge. I knew the name spelling looked familiar! Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Next dev meeting 25 January, 23:00 UTC (9 am east Australia, 11:00 Aotearoa/NZ, 12:00 Tahiti, 14:00 US west)
Hi :) Careful with the International Date Line, it's the 26th for on the west side. https://wiki.koha-community.org/wiki/Next_IRC_meetings Calendar: https://koha-community.org/calendar/ Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Tomorrow (Friday 2): Patch testing session to help enhancements and bug fixes to be released
Hi :) This is for the support providers that aren't used to testing patches and any provider that knows libraries where someone could be interested. To be forwarded to librarians, system librarians, educators, devs, sysadmins and other people that could be interested in contributing to Koha. Let's meet Friday the 2nd at any moment in the following timeframe: 13h-20h UTC / 8h-15h US East / 5h-12h US West The place is https://visio.chapril.org/koha (the text chat can be opened with the 4th button at the bottom: ️) Reminder of the modalities: The idea is to test patches to contribute to Koha. The biggest bottleneck for having more bugs fixes and enhancements is patch testing. Thus this call for getting together as Koha users. No need for particular skills, just basic Koha usage. You can come an leave at any moment, even for a short time it's possible to get simple stuff moving forward. We will use a VoIP call with chat tool to speak and eventually screenshare. It's possible to join without sound and only use chat. So if you are at the front desk and there are not much patrons you can still test patches ^^ So, whichever communication mode is the most convenient for you. No need to have a local Koha instance. Just with a web browser we can use the sandboxes [1] to have temporary Kohas to test most patches and do whatever we want without bad consequences. Here is a resource about how to test patches using sandboxes: https://wiki.koha-community.org/wiki/Sandboxes Cheers, [1] https://wiki.koha-community.org/wiki/Sandboxes -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Next Friday: Patch testing session to help enhancements and bug fixes to be released
Hi :) This is for the support providers that aren't used to testing patches and any provider that knows libraries where someone could be interested. To be forwarded to librarians, system librarians, educators, devs, sysadmins and other people that could be interested in contributing to Koha. Let's meet at any moment in the following timeframe: 13h-20h UTC / 8h-15h US East / 5h-12h US West The place is https://visio.chapril.org/koha (the text chat can be opened with the 4th button at the bottom: ️) Reminder of the modalities: The idea is to test patches to contribute to Koha. The biggest bottleneck for having more bugs fixes and enhancements is patch testing. Thus this call for getting together as Koha users. No need for particular skills, just basic Koha usage. You can come an leave at any moment, even for a short time it's possible to get simple stuff moving forward. We will use a VoIP call with chat tool to speak and eventually screenshare. It's possible to join without sound and only use chat. So if you are at the front desk and there are not much patrons you can still test patches ^^ So, whichever communication mode is the most convenient for you. No need to have a local Koha instance. Just with a web browser we can use the sandboxes [1] to have temporary Kohas to test most patches and do whatever we want without bad consequences. Here is a resource about how to test patches using sandboxes: https://wiki.koha-community.org/wiki/Sandboxes Cheers, [1] https://wiki.koha-community.org/wiki/Sandboxes -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Poll for a patch testing session to help enhancements and bug fixes to be released
Hi :) This is for the support providers that aren't used to testing patches and any provider that knows libraries where someone could be interested. To be forwarded to librarians, system librarians, educators, devs, sysadmins and other people that could be interested in contributing to Koha. Here is the poll: https://date.chapril.org/lauHXUSh6dcAV865 Reminder of the modalities: The idea is to test patches to contribute to Koha. The biggest bottleneck for having more bugs fixes and enhancements is patch testing. Thus this call for getting together as Koha users. No need for particular skills, just basic Koha usage. You can come an leave at any moment, even for a short time it's possible to get simple stuff moving forward. We will use a VoIP call with chat tool to speak and eventually screenshare. It's possible to join without sound and only use chat. So if you are at the front desk and there are not much patrons you can still test patches ^^ So, whichever communication mode is the most convenient for you. No need to have a local Koha instance. Just with a web browser we can use the sandboxes [1] to have temporary Kohas to test most patches and do whatever we want without bad consequences. Here is a resource about how to test patches using sandboxes: https://wiki.koha-community.org/wiki/Sandboxes Cheers, [1] https://wiki.koha-community.org/wiki/Sandboxes -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Need help to update coding guidelines with the replacement of jQueryUI Datepicker with flatpickr
Hi :) The coding guidelines still mention Datepicker. And we had a report that the change isn't straightforward and that some documentation would be useful. Any volunteer among the people who have a bit of understanding of the change and the usage? It had been suggestion to also have a ticket about this: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31741 Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Should we support MySQL? (either 5.7 or 8.0)
Hi :) The CI only tests MySQL 8 on main/master but it passes. Maybe we dropped strong support for MySQL years ago? And only kept MySQL 8 on master to catch the strict SQL mode issues? Because that's mostly how I hears about MySQL lately. (strict SQL mode) And I heard MySQL 5.7 still has the db increment issue so we likely don't want to support it. Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Forward this to librarians prone to contribute: Monday 26th: patch testing session to help enhancements and bug fixes to be released
Hi :) And also come, developers, admins, trainers, etc if you like a dedicated time with the community to test patches. Let's meet at any moment in the following timeframe: 13h-19h UTC / 14h-20h UK/ 9h-15h US East/6h-12h US West The place is https://visio.chapril.org/koha Here is a resource about how to test patches using sandboxes: https://wiki.koha-community.org/wiki/Sandboxes Modalities: The idea is to test patches to contribute to Koha. That's one of the **easiest and best way** to contribute to Koha. There is a huge need of testing to unblock patches and it would make a sizable difference in the pace of development of Koha if we reduce this bottleneck. No need for particular skills, just basic Koha usage. You can come an leave at any moment, even for a short time it's possible to get simple stuff moving forward. We will use a VoIP call with chat tool to speak and eventually screenshare. It's possible to join without sound and only use chat. So if you are at the front desk and there are not much patrons you can still test patches ^^ And also it's easier if you aren't comfortable with oral english. No need to have a local Koha instance. Just with a web browser we can use the sandboxes [1] to have temporary Kohas to test most of patches and do whatever we want without bad consequences. Cheers, [1] https://wiki.koha-community.org/wiki/Sandboxes -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Who runs the koha-jenkins IRC bot?
Hi :) It's about the move of automated output to #koha-bots Cheers, -- Victor Grousset/tuxayo ___ 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] Long-term support version of Koha (bug 31008)
Hi :) On 22-06-22 09:47, Paul Poulain wrote: Good thing to have a LTS, my main question is about the ecosystem around Koha. For example, how to manage Koha LTS regarding Debian/Ubuntu/ We already drop and gain support support for Debian/Ubuntu versions during the lifetime of Koha releases. Elastic Search/MariaDB... upgrades ? Same, we are getting patches for ElasticSearch 7 and OpenSearch support backported to oldoldstable. And in the past, I recall we dropped ES 5 support to fix a bug with ES 6. How can we be sure that, in 2 years, Koha LTS will become "unmaintainable" because it requires a Perl library that can't be upgraded and the underlying tool (OS, search engine...) isn't maintained anymore in the compatible version ? So it should be ok. Unless there are scenarios not covered by what we already do? Cheers, -- Victor Grousset/tuxayo ___ 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] Staff interface redesign is ready to be tested
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, -- Victor Grousset/tuxayo ___ 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] Gitlab policy changes
On 22-06-30 01:20, dc...@prosentient.com.au wrote: Let's see what Gitlab says. Yes, explaining the project and letting them decide is the best. Thanks Tomas for taking the time. Cheers, -- Victor Grousset/tuxayo ___ 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] Gitlab policy changes
On 22-06-29 04:00, dc...@prosentient.com.au wrote: [...] Victor, I'm not going to try to respond line by line to your message, No worries, what about the main point of my 1st message? That we don't fit at all with their terms when looking at our roles list no matter how we define maintainers. but I will say that everyone (myself included) has just been genuinely trying to interpret Gitlab's policy and how it applies to Koha; no one is trying to mislead anyone. The Koha community is the most good natured group of people that I've ever known in my entire life. Sorry that I have made many people uncomfortable. When I said «In practice we would be trying to scam GitLab.com» it was in «You don't realize it but it's misleading». Not «You are consciously and malevolently thinking to mislead them» [...] Anyway, I think that Tomas is going to try reaching out to Gitlab for more information, so we'll see what they say. Ultimately, we can speculate one way or another all we want, but it's up to Gitlab to say whether or not we fit, and I think that you can rest assured that we'll be open and honest with whatever information that they want to support their decision-making. Bringing up HLT or Koha Community as non profit organization to be able to tick the box «project maintainers are not seeking to make profit from this project by for example, selling services [...]» didn't look like «you can rest assured that we'll be open and honest with whatever information that they want to support their decision-making» Instead I though we gotta be upfront with ourselves if we were going that way which seemed misleading to me. (to bend so much things so they fit) And that we needed to find reasons to be morally ok with that. Cheers, -- Victor Grousset/tuxayo ___ 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] Gitlab policy changes
On 22-06-28 10:23, Jonathan Druart wrote: Sorry for the late reply, I didn't really know what to say. As I was involved earlier in the discussion I feel that by not replying, I am agreeing with your message, Victor. No worries, I think no one in the discussion was to be assumed to agree with the idea that it would be a scam attempt to apply as is for the non-profit program. Because for that someone must agree that we do not fit at all with the non profit criteria for maintainers. That's the main point of the message and necessary condition before starting to talk about the scam thing. And it seems everyone leans towards that we fit. So if anything to assume, is that everyone was leaning towards agreeing to apply in good faith without being a attempt to trick GitLab, thinking that we fit enough in the criteria. However I do not agree at all. I do not recognize myself in your words That's fine, it's my own view that we don't fit and the arguments to apply anyway with less moral remorse are only mine. > and I do not think "scamming gitlab" is a point of the discussion. The matter is to know if we are eligible for a program they support, and find the best way to apply in agreement with their terms and our project's view. Alright, looks good that way, I had to think hard to find moral justifications to apply as is without complying to their terms. (Assuming we would lean toward that we don't fit at all with their terms.) My feelings when reading the discussion were that bringing up Koha Community as an organization or Horowhenua Library Trust was very dubious and that we should be upfront that it would be a dubious application to their program. Thus the scam thing. We are relying quite a lot on gitlab, and I personally think the open source product they provide is great. I thank their team for that. With this answer, I only wanted to take distance with your words. What about the main point of the message? My most important words are that we don't fit at all with their terms. (details in previous message) Sorry that I went too far developing the scam thing that it took all the attention. Cheers, -- Victor Grousset/tuxayo ___ 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] Effective circulation rule preview/tester
Hi :) IIUC part of solution is in: Bug 23732 - Hold rules checker: show matched rules and syspref values to help understand why a hold is possible or not If you are interested in testing and reviewing the code, that can motivate me to get it ready this cycle. I tried in the previous cycles and it's mostly done but I still have a number of details, corrections and some automated testing to add. -- Victor Grousset/tuxayo ___ 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] Gitlab policy changes
On 22-05-26 01:55, dc...@prosentient.com.au wrote: In theory, the organisation should be the Koha Community so it might be OK, since it doesn't sell services. In practice we would be trying to scam GitLab.com If we look at https://wiki.koha-community.org/wiki/Roles_for_22.11 and count for Release Manager, QA team, RMaints, Packaging Team, Translation Manager. We have around 17 people and between 11 and 12 are working or subcontracting for private support companies. (Assuming they are all for profit because unfortunately, almost no one does non profit companies even though that totally works to make a living out of one's business.) We might not have remorse in trying to scam a publicly traded company but we should be aware among ourselves that's the plan. On 22-05-26 12:39, Jonathan Druart wrote: > There is a checkbox on the form > That's the only reason I haven't filled in the form already, it's not > clear to me if we are eligible or not. Reading the checkbox, it looks clear that no matter how we want to define maintainers. There are way too much in proportion that are seeking to make a profit that we can't in good faith try to negotiate that we still fit the criteria. We can still try and be upfront and present the project and hope that they want to support it. Or try to scam them without remorse because why not. It's not like GitLab is very respectable since they are publicly traded and the full version of GitLab include proprietary parts. And self-host the workers if that fails. Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Development IRC meeting tomorrow at 21:00 UTC (good hour for most of Oceania and Americas)
Hi :) https://wiki.koha-community.org/wiki/Development_IRC_meeting_8_June_2022 -- Victor Grousset/tuxayo ___ 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] String patch needing review to clean a lot the translations
On 22-05-30 05:05, Victor Grousset/tuxayo wrote: So if anyone can take a look at 30733 even for a partial review of the code that would be awesome. Because this patch would be a huge help for translators as it gets rid of most of the terrible to translate strings. Fridolin did a first review and found some points that have been addressed. Since they are in the QA team let's keep the ticket in "Need Signoff" to have a wider pool of potential reviewers and Fridolin will do the QA step next. So everyone still welcome to take a look at the changes. The goal is to have this merged and backported to 22.05 before the 22.05.01 string freeze which is the 15th. So the translators still catching up on 22.05 or older work will be able to benefit from these changes. Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] String patch needing review to clean a lot the translations
Hi :) It's Bug 30733 - Simplify translatable strings https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30733 The sooner this can be merged, the more work it will spare for translators that are currently working on 22.05 because it's still early enough to be backportable. We have an opportunity to clean a lot of the strings that are an absolute pain to translate. The long ones with tons of %s %s %s %s %s part of which must be retranslated over and over each version when one thing has changed. They can be fixed with the same simple method as Bug 29602 - We must be nicer with translators That is adding tags around the strings to have nice broken down approach. So if anyone can take a look at 30733 even for a partial review of the code that would be awesome. Because this patch would be a huge help for translators as it gets rid of most of the terrible to translate strings. Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.11.19 released
Hello! :) The Koha Community is happy to announce the release of Koha 20.11.19 The full release notes can be found at: https://koha-community.org/koha-20-11-19-released Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Analysis help needed for one of the last pieces for ElasticSearch 7 support
Hi :) Bug 25669 has stalled on the choice of two options, it needs a confirmation that one of the alternative patches implements indeed one of the two options which is enough for just ES 7 support and raises no question about additional configuration work unlike the other option. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25669 Bug 25669 - ElasticSearch 6: [types removal] Specifying types in put mapping requests is deprecated (incompatible with 7) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.11.18 released
Hello! :) The Koha Community is happy to announce the release of Koha 20.11.18 The full release notes can be found at: https://koha-community.org/koha-20-11-18-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Vote: Use Vue3 for the new ERM (Electronic Resource Management) module
Hi :) At last meeting, today, it has been voted to give a go to have Vue3 JS framework be used for the new ERM module. Here is the same question to have a wider reach than only the people that were able to attend. So, agreed with that? Or any objections? Let's wait a few days and if no major objection, Jonathan will be able to continue the ERM module knowing Vue won't be a problem for the patch acceptance in Koha. meeting logs: http://irc.koha-community.org/koha/2022-04-20#i_2416969 Email asking for the vote and listing all the resources about the ERM project https://lists.koha-community.org/pipermail/koha-devel/2022-April/046998.html Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Terminology: addition of "use restriction, not debarment"
Hi :) After last dev meeting of the 6th, the following addition has been done: https://wiki.koha-community.org/w/index.php?title=Terminology=historysubmit=30449=30265 Whole page: https://wiki.koha-community.org/wiki/Terminology Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Collecting ideas to have an easier time with large patch submissions. And inventory of large submissions that are stuck.
Hi :) At the development IRC meeting of 6 April 2022 it was discussed what could be done to help large developments better move forward using the recent experience with recalls patches (bug 19532). Here is what came out of it: - resist scope creep and ask only for necessary changes for inclusion (Minimun Viable Product) - ask to focus discussions on concrete actions for the dev to reach an acceptable MVP - note somewhere all the potential follow ups ideas so that they don't get lost and it easier to move on knowing they are somewhere not lost - bring the development as a topic in meetings and QA team discussions to get focus on it What do you think of these? Any other ideas/guidelines to complete this? What are the large patch submissions that are stuck that you know about? If you could send messages in the past in the ticket, what would you sent that would have hopefully helped it move forward? Here are some other ideas: - When submitting large changes, submit a minimal version first if possible and if a more complete version might be too much. Even if it will be hard to maintain a separate more complete version for your customers. If it gets stuck, it will be worse than doing it in chunks. - Maybe reboot a submission on a new ticket with a chopped down version if noticing you should have went for the previous guideline. - Maybe propose taking on testing complicated stuff of someone else if they do the same for your submission. It will be worth your time if it avoids being stuck for months/years with dozens of rebases on the ticket plus on your customer's Kohas due to it being a effectively a fork. Cheers, -- Victor Grousset/tuxayo ___ 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] Release maintenance: Monthly string freeze: shall it be announced also on koha-devel and the general list?
On 22-03-24 21:07, Katrin Fischer wrote: I think as we have a dedicated list we should not do too extensive cross posting. But if we wan to send to a second list, maybe Koha? Ok let's roll with that :) -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.11.17 released
Hello! :) The Koha Community is happy to announce the release of Koha 20.11.17 The full release notes can be found at: https://koha-community.org/koha-20-11-17-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Release maintenance: Monthly string freeze: shall it be announced also on koha-devel and the general list?
Hi :) The idea is to push the librarians, admins, and devs to check the translations out if they remember something off. To try to reach out instead of relying on those already interested in translation and subscribed to koha-translate. Currently not all release maintainers announce the string freeze in the same place resulting in confusion. Cheers, -- Victor Grousset/tuxayo ___ 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] I played with Cypress (and ERM and Vue)
Hi :) Nice to hear that. How was coding UI tests compared to Selenium? And the API tests compared to the current way? It's good that Cypress provides an alternative to both. The Cypress section of this comparison with Puppeteer, Selenium, and Playwright was not impressive compared to Puppeteer and Playwright. https://www.testim.io/blog/puppeteer-selenium-playwright-cypress-how-to-choose/ And it seems some parts of Koha (with pop up windows) wouldn't be testable with Cypress :o https://docs.cypress.io/guides/references/trade-offs#Multiple-tabs and I think the workaround wouldn't work for us since our pop ups are used to fill a field in the calling window: https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/testing-dom__tab-handling-links Also about iframes, with Firefox, Cypress can't at all interact inside them. Could that be an issue if one day we want to use Cypress in Koha? Given that Koha has a few minor iframes. But it's the only Selenium alternative in the 3 to have a community development. As opposed to Puppeteer and Playwright being developed >95% by Google and Microsoft respectively. So who knows if one of the two has so much success that Google or Microsoft drops their efforts on maintaining the other one. Or one looses traction. It's not the first time they would drop support to a project[1] and Firefox support should be expected to always be precarious. (it's still experimental for Puppeteer) On the other hand it's libre/open source so we can hope on the long term there will always be a community to do the minimal maintenance. Hard to say about Firefox support though. [1] There is some dev stuff the following lists. Not enough to be certain of the risks. (So I'm might be spreading FUD due to GAFAM allergy) But enough to be wary about projects whose top committers are from a single company. Which totally have the right to change their priorities, no issues with that. https://killedbygoogle.com/ https://killedbymicrosoft.info/ Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Additional DB indices for Koha?
Hi :) Has there already been the need of additional DB indices for Koha? To speed up some queries that doesn't use a primary or foreign key. From what I see in kohastructure.sql , there is no index besides the implicit ones for keys. Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Need help to test a patch that will simplify translations
Hi, After a few iterations of testing and fixes, bug 29602 looks about ready. It mostly needs someone else to signoff by testing that pages are not broken. Here is a ticket with a link to the comment listing most of the impacted pages: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29602#c50 Rereading the last follow-up patches would also help. Let me know if I can be of any help. Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 20.11.17 has begun
Hi, String freeze is into effect as of now for the 20.11.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.11, then you must also copy it to 21.05 and 21.11. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha security release available ⚠
Hello! :) The Koha Community is happy to announce the release of Koha 21.05.12, 20.11.16, 19.11.27. The previous release of 21.11.03 already contained the fixes. Users are advised to upgrade their Koha to these versions The full release notes can be found at: https://koha-community.org/koha-21-05-12-released https://koha-community.org/koha-20-11-16-released/ https://koha-community.org/koha-19-11-27-released/ The latest Koha packages and tarballs are ready. Thanks to everyone involved :) -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.11.15 released
Hello! :) The Koha Community is happy to announce the release of Koha 20.11.15 The full release notes can be found at: https://koha-community.org/koha-20-11-15-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 20.11.15 has begun
Hi, String freeze is into effect as of now for the 20.11.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.11, then you must also copy it to 21.05 and 21.11. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 20.11.14 has begun
Hi, String freeze is into effect as of now for the 20.11.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.11, then you must also copy it to 21.05 and 21.11. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Call for volunteers to work on ElasticSearch 7 support (ES6 will be EOL on February 8)
Hi :) After ES6's EOL, if another vulnerability if found in Log4J for example, Koha instances using ES won't be able to patch it. Here is the omnibus ticket: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25439 There are *at least* a 1/3 of them that look quite easy. Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.11.13 released
Hello! :) The Koha Community is happy to announce the release of Koha 20.11.13 The full release notes can be found at: https://koha-community.org/koha-20-11-13-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 20.11.13 has begun
Hi, String freeze is into effect as of now for the 20.11.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.11, then you must also copy it to 21.05 and 21.11. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Proofreading request of Koha's Wikipedia article release history table
Hi :) https://en.wikipedia.org/wiki/Koha_(software)#Releases Let me know if something is wrong. For 19.11 being oldoldoldoldstable , it's getting ridiculous but it should be correct. 20.11 is oldoldstable 20.05 even though it's EOL it's now oldoldoldstable So 19.11 must be oldoldoldoldstable XD Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.05.18 released (last release for 20.05.x)
Hello! :) The Koha Community is happy to announce the release of Koha 20.05.18 This is the last release for the 20.05.x branch, you are strongly encouraged to upgrade to later releases in order to continue to get security and bugfix support as well as translation updates. The full release notes can be found at: https://koha-community.org/koha-20-05-18-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 20.05.18 has begun (last release for 20.05.x so no more translation update after)
Hi, String freeze is into effect as of now for the 20.05.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.05, then you must also copy it to 20.11, 21.05 and 21.11. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo ___ 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] custom core patches management
How is your Koha installed? Debian packages? -- Victor Grousset/tuxayo ___ 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 20.05.17 released
I had only saved the post as a draft, thanks Jonathan for publishing it. Cheers, -- Victor Grousset/tuxayo ___ 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 20.05.17 released
On 21-11-02 09:42, Michael Kuhn wrote: This URL does not lead to the release notes. Can you please give us the correct URL? Can you retry? It works for me even in private browsing so maybe someone fixed it. I usually check the link before sending the email but I missed this time. Thanks for checking :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Translation: One week remaining to complete 21.05 translation to avoid some duplicate work when 21.11 will be out
Hi :) If your languages of choices don't have yet a full translation for Koha 21.05, it's a good time to put as much a possible work towards that. Because in a week, the 10th will be the string freeze to prepare the major release of Koha 21.11 which the scheduled around the 26th. At that moment, translation of 21.05 will be copied as a starting point for 21.11. After that, any translation work on 21.05 will have to be copied to 21.11. If you usually translate multiple versions, that will spare you one copy compared if you do it after the 10th. If you usually only translate the latest version, it will still help people that will stay on 21.05 to benefit from your work. ↓↓↓ https://translate.koha-community.org/projects/21.05/ ↑↑↑ Happy translating :) -- Victor Grousset/tuxayo ___ 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] More handy fixes in Zebra 2.2.3
good news, thanks for the bug reports :D -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.05.17 released
Hello! :) The Koha Community is happy to announce the release of Koha 20.05.17 The full release notes can be found at: https://koha-community.org/koha-20-05-17-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Any support provider doing yearly major upgrades on XX.05 versions?
Hi :) I know about people upgrading every 6 month, so every major version. And others upgrading yearly on XX.11 version to do the upgrade before summer when the version has had a lot user feedback. And I'm wondering if there are some people doing the same but with XX.05 ? And at which moment of the year? Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Translation platform sync delay: 2nd call to translators to prepare this month's minor release
Hi, Due to a delay in getting the platform in sync with the to-be-released code, the new strings came Wednesday. So translators are advised to take another look to translate these: https://translate.koha-community.org/ The minor releases of 21.05.x 20.11.x 20.05.x 19.11.x will be around the 27th. Happy translating :) -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 20.05.17 has begun
Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 20.05.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.05, then you must also copy it to 20.11 and 21.05. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo ___ 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] Can we add HTML classes to add semantic to elements when writing automated UI tests?
On 21-09-30 08:21, Jonathan Druart wrote: Yes, assign a class or id to the element. This is done several times in basic_workflow.t great, right, I could use ids also Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Can we add HTML classes to add semantic to elements when writing automated UI tests?
Hi :) I'm writing an UI test for creating a club to later use it for holds. In the page /cgi-bin/koha/clubs/clubs.pl There is the button "New club" , I would like to click on it but it has nothing in the classes or id that tells it's this button. I could use a vague and fragile in the long run selector like ".main .dropdown-toggle" and comment explaining what it is. Or I could add a class like "new-club" to the Maybe there is a way I missed to have a readable, concise and durable way to click on the dropdown button but the question will still stand for a future case way there won't be such a way. Also maybe there is better class name than "new-club". The naming practice is also an important question. Cheers, -- Victor Grousset/tuxayo ___ 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] Release Manager for 22.05
Fantastic news! :D The roles_for_22.05 page has not been created on the wiki if I'm not wrong, shall I create it ? Here it is, since today https://wiki.koha-community.org/wiki/Roles_for_22.05 cc Fridolin Cheers, -- Victor Grousset/tuxayo ___ 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] Call for news - Newsletter September 2021
On 21-09-25 08:49, JESSE KAH wrote: Good suggestion though. The Chinese translation is desperately required by one of our client that time, so we translate in our way for faster result. (*^__^*) We will get our people to go one-by-one to upload there then. Great! :D But fear not, you shouldn't need to do it one-by-one, it's possible to upload all the translations to replace the existing ones. Cheers, -- Victor Grousset/tuxayo ___ 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] Call for news - Newsletter September 2021
Hi :) On 21-09-21 10:08, JESSE KAH wrote: Update from my previous email for *Chinese Translation*: Development on*Full Chinese Simplified Translation*on Koha version 20.11 accomplished. Users may download via https://drive.google.com/drive/folders/13HPm3xXHEPPZa9YCu65CTAfwUoWnVQ5x?usp=sharing <https://drive.google.com/drive/folders/13HPm3xXHEPPZa9YCu65CTAfwUoWnVQ5x?usp=sharing> for the full Chinese features of it. Congratulations on having the translation complete! It was only around half complete before. Do you have plans to integrate it directly into Koha via the translation platform? https://translate.koha-community.org/zh_CN/20.05/ So it will be available without any action to all zh_CN Koha installations. It's also the first step to enable the translation to be kept version to version which will also benefit your and your customers in the future upgrades. I can guide you or one of your colleagues for the procedure. It should be something like this - you create an account on the translation platform - I'll make a request so your account get the direct translation rights for zh_CN - you upload your files in the platform Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 20.05.16 has begun
Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 20.05.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.05, then you must also copy it to 20.11 and 21.05. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo ___ 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] Perl advice for checking hash content
On 21-08-30 11:07, Jonathan Druart wrote: Keep it simple, why not the following? Because I didn't think of it :O Thanks a lot, tests fixed! Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Perl advice for checking hash content
Hi :)
For a development, I'm adding additional keys to
C4::Reserves::CanItemBeReserved returned hash.
But there are a bunch of tests that match the whole return value and
thus don't expect the new keys in the hash.
Here is the best way so far I've found to adapt it.
is_deeply(
CanItemBeReserved( $patron->borrowernumber, $itemnumber_2 ),
{ status => 'tooManyReservesToday', limit => 0 },
'Patron cannot reserve if holds_per_day is 0 (i.e. 0 is 0)'
);
↓
my @status_and_limit = @{CanItemBeReserved( $patron->borrowernumber,
$itemnumber_2 )}{"status", "limit"};
is_deeply(
\@status_and_limit,
['tooManyReservesToday', 0],
'Patron cannot reserve if holds_per_day is 0 (i.e. 0 is 0)'
);
How could this be better?
Since it took me more than two hours only to have something that works
and without warnings. There are surely other ways to do it™, and
hopefully a nicer one.
Most of the time was reading and learning by trial and error about
referencing and dereferencing and the specifics or Perl hashes and
array. It's odd to have been working 3.5 years on Koha closer to the
code than to the librarian stuff and only have to really start learning
Perl now ^^
Away, this is why advice is needed to have something that fit the good
practices :)
Key/Value Hash Slices would allow to not change the expected param of
is_deeply() but that doesn't really look different for the readability.
And isn't worth having Koha bump minimal Perl version from 5.14 (2011)
to 5.20 (2014). Ok it's just for running the tests and not production
but still. -> very minor or inexistent readability improvement.
https://perldoc.perl.org/perldata#Key/Value-Hash-Slices
Having two assertions (is() calls) for status and limit would allow a
simpler syntax but add duplication.
Cheers,
--
Victor Grousset/tuxayo
___
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/
[Koha-devel] Koha 20.05.15 released, ⚠ security release
Hello! :) The Koha Community is happy to announce the release of Koha 20.05.15 The full release notes can be found at: https://koha-community.org/koha-20-05-15-released/ The Debian packages are already available. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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] Replacement of mailman (mailing lists)
On 21-08-19 08:42, dc...@prosentient.com.au wrote: It does seem like Discourse is reasonably popular although I’ve only engaged with it from the forum perspective. It looks like it does have mailing list support but I don’t know what that means exactly. https://meta.discourse.org/t/what-is-mailing-list-mode/46008 > In mailing list mode you will receive one email per post, as happens with traditional mailing lists. This is desirable if you prefer to interact via email, without visiting the forum website. https://meta.discourse.org/t/what-is-mailing-list-mode/46008/10 > Yes, provided you configure “email reply support” appropriately I just checked on an instance and it's possible to watch a category. It would have the same effect as subscribing to a mailing list. --- Also, it's possible if it's worth the work to import a mailing list. https://meta.discourse.org/t/discourse-vs-email-mailing-lists/54298/1 see => How do I import my mailing list? => My organisation manages multiple mailing lists. Can they be imported incrementally? Cheers, -- Victor Grousset/tuxayo ___ 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] Improvement of our upgrade process
Hi :) This is great news, thank for the summary. On 21-08-17 11:16, Jonathan Druart wrote: Let me know if you have any questions! I wonder how often «say $out "Update is going well so far";» will be left in submitted patches. Let's try like that ^^ Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 20.05.15 has begun
Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 20.05.x maintenance branch. The minor release is scheduled for around the 23th. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.05, then you must also copy it to 20.11 and 21.05. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.05.14 released
Hello! :) The Koha Community is happy to announce the release of Koha 20.05.14 The full release notes can be found at: https://koha-community.org/koha-20-05-14-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.11.08 released
Hello! :) The Koha Community is happy to announce the release of Koha 20.11.08 The full release notes can be found at: https://koha-community.org/koha-20-11-08-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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] Bug 17600 (Standardize the EXPORT) is pushed
On 21-07-16 09:02, Jonathan Druart wrote: I've described in the commit message what it is doing, please read it. thanks for the guidelines about conflict resolution :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 20.05.14 has begun
Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 20.05.x maintenance branch. The minor release is scheduled for around the 23th. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.05, then you must also copy it to 20.11 and 21.05. Otherwise your work will be lost for future versions. (We've had a recent significant case of that!) Happy translating, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.11.07 released, ⚠ security release
Hello! :) The Koha Community is happy to announce the release of Koha 20.11.07 The full release notes can be found at: https://koha-community.org/koha-20.11.07-released Debian packages should be available shortly. Thanks to everyone involved :) Fridolin will be back for the next release, I’m just replacing them for this one. Cheers, -- Victor Grousset/tuxayo ___ 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] pull latest koha-testing-docker-images (Add new lib directory)
On 21-06-24 15:57, Jonathan Druart wrote: I've just pushed bug 28489 that is adding a new "lib" directory. Isn't it this one instead ? Bug 28519 - Add a 2nd directory for Perl modules https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28519 Cheers, -- Victor Grousset/tuxayo ___ 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] pull latest koha-testing-docker-images (Add new lib directory)
Thanks for the heads up :) -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 20.05.13 released, ⚠ security release
Hello! :) The Koha Community is happy to announce the release of Koha 20.05.13 The full release notes can be found at: https://koha-community.org/koha-20.05.13-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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] Replacement of mailman (mailing lists)
On 21-06-23 12:27, Julien Sicot wrote> I also see the opportunity to merge in one point all the koha communities by using groups (geographical or languages communities like kohala in France that use separate mail discussion list). Yes, this is great! It would be a very easy way to create a discussion space for sub-communities. Without a website or mailing list. And it would be very discoverable. As someone must be lucky to stumble on this page: https://wiki.koha-community.org/wiki/Koha_Users_Groups While we are at it, anything missing on it? ^^ Cheers, -- Victor Grousset/tuxayo ___ 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] Replacement of mailman (mailing lists)
Hi :) On 21-06-04 16:03, Jonathan Druart wrote: The question is: do we make the work to keep mailman, or do we consider it obsolete and we need something more modern? I think that a forum software would help users ask and answer more questions. As well as having them indexed by search engines. "Just" upgrading mailman to v3 and more administrating would be nice for the reasons you exposed. And v2 still stores the passwords as plaintext. And as a provocation (or honesty?) it sends them back to oneself every month ^^ Anyway, that would still be a good outcome. The final outcome might depend more on who are in a good position to do one of the paths. Anyone(s)[1] feeling like being such a position? Cheers, -- Victor Grousset/tuxayo [1] I know it's not valid english :P ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 20.05.13 has begun
Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 20.05.x maintenance branch. The minor release is scheduled for around the 22th. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.05, then you must also copy it to 20.11 and 21.05. Otherwise your work will be lost for future versions. (We've had a recent significant case of that!) Happy translating, -- Victor Grousset/tuxayo ___ 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] Sharing installation method with Hea
Hi :) On 21-06-15 01:47, dc...@prosentient.com.au wrote: I was looking at https://hea.koha-community.org/systempreferences <https://hea.koha-community.org/systempreferences> to view the different versions of Koha out there, and it got me thinking how it would be nice to know how people install Koha. I imagine that we all think that the majority of people use the Debian packages, but it would be good to know. What do people think? Does Koha already have data that would allow to deduce the install method? If not, how to infer that for Debian packages? For a git install, checking for a .git is enough. Cheers, -- Victor Grousset/tuxayo ___ 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] Deadlock issues when running the tests in parallel, and maybe not only in the tests?
Thanks folks for the replies. So I was running manually the test suite, and used -j from the CI but didn't used --rules so that's why it was failing. -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 19.11.18 released, ⚠ security release
Hello! The Koha Community is happy to announce the release of Koha 19.11.18 The full release notes can be found at: https://koha-community.org/koha-19-11-18-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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] Deadlock issues when running the tests in parallel, and maybe not only in the tests?
Hi :) On 21-05-25 18:00, Joonas Kylmälä wrote: Hmm, based on the line https://gitlab.com/koha-community/koha-testing-docker/-/blob/master/files/run.sh#L204 I would think the ENV variable is actually set so maybe it is not this. Any more info on the tables it locks on? I did yet processed your previous message but here quickly the error messages. Important info, it has been ran on 19.11.x t/db_dependent/Charset.t ok ===(4190;485 797/? 0/? 17/47 2/15 )DBD::mysql::db do failed: Deadlock found when trying to get lock; try restarting transaction [for Statement "DELETE FROM issues"] at t/db_dependent/Circulation/Branch.t line 49. ===(4191;486 797/? 0/? 17/47 3/15 )DBD::mysql::db do failed: Deadlock found when trying to get lock; try restarting transaction [for Statement "DELETE FROM items"] at t/db_dependent/Circulation.t line 1174. # No tests run! # Failed test 'No tests run for subtest "AllowRenewalIfOtherItemsAvailable tests"' # at t/db_dependent/Circulation.t line 1269. DBD::mysql::db do failed: Deadlock found when trying to get lock; try restarting transaction [for Statement "DELETE FROM items"] at t/db_dependent/Circulation.t line 1174. # Looks like your test exited with 255 just after 18. t/db_dependent/Circulation.t Dubious, test returned 255 (wstat 65280, 0xff00) -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Deadlock issues when running the tests in parallel, and maybe not only in the tests?
Hi :) IIUC this is where the CI calls "prove" to run the tests https://gitlab.com/koha-community/koha-testing-docker/-/blob/master/files/run.sh#L213 And this is the place where KOHA_PROVE_CPUS is set. https://gitlab.com/koha-community/koha-testing-docker/-/blob/master/files/run.sh#L155 It's not set in ".env" file so it should use "nproc" and this calls "prove" with more than one thread. Is that really the case? I tried locally use to "prove -j 4" and I'm getting deadlocks with the database after a few minutes. And do these deadlock in tests mean that Koha can hit them while running in production? I expect the tests to fail due to messing up with each other data but a deadlock is something else. Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 19.11.18 has begun
Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 19.11.x maintenance branch. The release is scheduled for around the 24th/25th. **If you missed it the upcoming 21.05 release is translatable now.** This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 19.11, then you must also copy it to 20.05, 20.11 and 21.05. Otherwise your work will be lost for future versions. (We've had a recent significant case of that!) Happy translating, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Help needed to test a bug, knowledge required: running automated tests
Hi :) Here is a bug that I tested and checked for QA. Now a test from someone else is needed. Here is the ticket: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28200 Here is the test plan: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28200#c16 If you have any questions[1] I'll gladly guide you via email or chat (nickname: tuxayo) [1] including setting up a Koha environment from scratch. Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Help needed to test an i-tiva bug (no prior knowledge required)
Hi :) Here is a bug that I tested and checked for QA. Now a test from someone else is needed. Here is the ticket: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27562 Here is the test plan: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27562#c4 Here are instructions to setup i-tiva: https://wiki.koha-community.org/wiki/External_Integration#i-tiva I'll gladly guide you via email or tchat (nickname: tuxayo) Cheers, -- Victor Grousset/tuxayo ___ 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] Elasticsearch vs OpenSearch
Hi :) Found another legal analysis that contradicts the first one: https://writing.kemitchell.com/2021/01/20/Righteous-Expedient-Wrong.html Even if contradictory, that still helps to understand the situation. Divergence still means something about the eventual risks. Some thoughts after reading: "SaaS capture”, “Amazon problem”, “Google problem” are legitimate concerns. But this controversy shows how hard it is to address it. Even if the copyleft doesn't affect Koha. It seems clear that it affects management services (what is the extent of that?). So what about if a hosting management tool is under a copyleft license? IIUC it can't be released under the SSPL. So that would force to only use permissive licensed management tools. So it's not a legal blocker but that restrict possibilities. And actually leads to a loss of freedom on these tools because copyleft software help about that. Some non-Koha thoughts: 1. Does having the hosting management tools of Amazon or Google or Microsoft would really help not them having a quasi monopolistic share on the hosting of databases et other tools? (public interest PoV) Well actually it's to have them buy the version with the other license. 2. Do ElasticSearch actually lacks money to maintain the same level of work on the ES stack and give the investors a reasonable return of investment? (accounting that it was a risky one so the return should be more than the average) As for the second part, there is actually no limit on the ROI (imagine if loans worked like that, lol), especially with venture capital. So there can be doubt on the legitimacy of the additional need of revenue. Cheers, -- Victor Grousset/tuxayo ___ 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] Optimizing Starman startup
Great results! Thanks for pushing this :) On 21-04-29 02:00, dc...@prosentient.com.au wrote: As I mentioned before, we probably won't be able to skip the validation for years, unless we roll our own Mojolicious::Plugin::OpenAPI... Or install via CPAN for instances that are facing the issue? Cheers, -- Victor Grousset/tuxayo ___ 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] git trick for compiled CSS
Thanks! Great tricks. Added to the wiki: https://wiki.koha-community.org/wiki/Working_with_SCSS_in_the_OPAC_and_staff_interface#Reviewing_changes_of_the_compiled_CSS_file -- Victor Grousset/tuxayo ___ 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] Optimizing Starman startup
Hi :) On 21-04-28 06:40, dc...@prosentient.com.au wrote: But now that I think about it again... Jan's change is actually all we need. That's a good news :D So what are the perf results of this? IIUC for your use case (spawning 120 workers with a 10 core CPU) * 2 minutes 45 seconds before bug 24700, i.e. < 20.05 * 1 minute 30 seconds Koha >= 20.05 * 20 sec when validation could be disabled with a future version of Mojolicious::Plugin::OpenAPI -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 19.11.17 released
Hello! The Koha Community is happy to announce the release of Koha 19.11.17 The full release notes can be found at: https://koha-community.org/koha-19-11-17-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 19.11.17 has begun
Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 19.11.x maintenance branch. The release is scheduled for around the 23th. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 19.11, then you must also copy it to 20.05 and 20.11. Otherwise your work will be lost for future versions. Happy translating, -- Victor Grousset/tuxayo ___ 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] Elasticsearch vs OpenSearch
Hi :) On 21-04-16 02:23, dc...@prosentient.com.au wrote: Because I’m good at stirring up trouble… XD > AWS have forked the last FOSS Elasticsearch (7.10 I think) Hopefully AWS won't be the only one doing all the work and having all the control. (Red Hat, SAP, Capital One, CrateDB, Aiven and Logz.io are said to be part of it) They’ve announced that they’re calling it OpenSearch. It’s still only in alpha stage and they won’t have a production-ready release for months yet, but it is interesting to keep notes on. Great news to see this moving. Because the topic will come in the future. Since ES isn't libre/open source anymore, ES even acknowledges that. https://www.elastic.co/pricing/faq/licensing#what-is-sspl-and-how-does-it-work? There is a lot written stuff and contradictory analysis on the topic. But regardless of what the ES FAQ and blog posts says. **Is there a reliable legal analysis on the license text?** The closest thing I have found so far is this one: https://anonymoushash.vmbrasseur.com/2021/01/14/elasticsearch-and-kibana-are-now-business-risks#page-title Found also people dismissing it as FUD but without contradictory legal analysis. The key question are: Is Koha legally usable with SSPL ES? Is it's affected by it's copyleft clause? (up) Same question for the underlying components used to run ES. (down) Elastic are responsible for the vast majority of commits in Elasticsearch, so I’m somewhat skeptical about a fork, but I think there is a lot of anger at Elastic and a lot of support for OpenSearch, so who knows. The last libre version of ES is pretty great as it is. Not having the fastest possible development on OpenSearch won't take away that. I don’t think there’s anything to do at this stage, but just wanted to share the information for people +1, thanks. -- Victor Grousset/tuxayo ___ 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] Second look needed on a few (2!) lines related to plugins
On 21-03-30 01:31, Mason James wrote: hiya, here's some info... https://docstore.mik.ua/orelly/perl3/prog/ch03_16.htm Indeed there is a trinary, but it's about if it makes sense to do "those things" related to plugins. Is that useful, is that valid, is that enough? Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Second look needed on a few (2!) lines related to plugins
Hi :) It's about Bug 25476 - Uploaded files can't be easily browsed via upload.pl There are two lines in the patch that are out of my knowledge to QA: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25476#c6 [% PROCESS plugin_pars %] [...] $plugin? ( public => 1 ): () Does this look familiar to anyone? Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 19.11.16 released
Hello! The Koha Community is happy to announce the release of Koha 19.11.16 The full release notes can be found at: https://koha-community.org/koha-19-11-16-released/ Debian packages will be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 19.11.16 has begun
Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 19.11.x maintenance branch. The release is scheduled for around the 23th. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 19.11, then you must also copy it to 20.05 and 20.11. Otherwise your work will be lost for future versions. Happy translating, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Koha 19.11.15 released, security release ⚠
Hello! The Koha Community is happy to announce the release of Koha 19.11.15 The full release notes can be found at: https://koha-community.org/koha-19-11-15-released/ Debian packages will be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo ___ 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/
[Koha-devel] Time to translate: string freeze to prepare Koha 19.11.15 has begun
Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 19.11.x maintenance branch. The release is scheduled for the 22th. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 19.11, then you must also copy it to 20.05 and 20.11. Otherwise your work will be lost for future versions. Happy translating, -- Victor Grousset/tuxayo ___ 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/
