14:00:32 #startmeeting Development IRC meeting 16 June 2021 14:00:32 Meeting started Wed Jun 16 14:00:32 2021 UTC. The chair is Joubu. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:32 The meeting name has been set to 'development_irc_meeting_16_june_2021' 14:00:48 #link Development_IRC_meeting_16_June_2021 14:00:55 #link https://wiki.koha-community.org/wiki/Development_IRC_meeting_16_June_2021 14:00:58 rmaint in also wainui 14:00:59 #topic Introductions 14:01:00 *es 14:01:03 *is 14:01:06 #info Jonathan Druart 14:01:19 #info Tomas Cohen Arazi, Theke Solutions 14:01:21 The bot (wahanui) is not here, tuxayo 14:01:33 #info Thomas Dukleth, Agogme, New York City 14:01:40 Joubu: that's why I'm doing the job manually ^^" 14:01:41 #info Martin Renvoize, PTFS Europe, UK 14:01:52 low-tech++ 14:01:56 #info tuxayo/Victor Grousset, France 14:01:56 * ashimema is on the school run, but will try to join by phone 14:02:16 #info Henry Bolshaw, House of Lords, UK 14:02:25 #info Nick Clemens, ByWater Solutions 14:03:20 cait1, are you around? 14:03:24 #topic Announcements 14:03:26 (keep the info for roadmap's topics for later) 14:03:43 #info Fridolin Somers, Biblibre, France 14:04:00 * fridolin waves 14:04:12 About the meeting facilitator role, I will join ashimema. We are going to prepare the meetings, like 2 days in advance 14:04:31 we will ping people with #actions and those who added topics to the agenda 14:04:52 the idea is to collect info ahead of the meeting 14:05:05 so please answer us if you get an email :) 14:05:10 something else? 14:05:13 +1 14:05:15 oh sorry 14:05:16 yes 14:05:20 #info Katrin Fischer, BSZ, Germany 14:05:24 superbe 14:05:48 Thanks for the support Joubu.. apologies the meetings so far have caught me by surprise a bit 14:05:59 #topic Update from the Release manager (21.11) 14:06:18 Basically everything is (too) quiet, although we have tons of things planned :) 14:06:27 1. Jenkins is red for a couple of days because of the "ugly patch" for the YAML::XS serializer for CGI::Session. 14:06:35 We moved it to a lib directory and bug 28519 that is waiting for QA. 14:06:35 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28519 enhancement, P5 - low, ---, dcook, Signed Off , Add a 2nd directory for Perl modules 14:06:40 I will push it tomorrow if nobody PQA it (!) 14:06:44 We need it for the 21.05.0 14:07:01 I expect no strings with that, but plz keep string freeze in mind 14:07:13 hi khall :) 14:07:14 for other patches 14:07:15 2. I sent some emails for the roadmap topics (more info in the dedicate agenda topic) and I am starting to prioritize them (will depend on the reply I get) 14:07:45 3. Also sent an email to koha-devel about the early-push candidates for 21.06 14:07:46 Sorry, my QA time has been zero so far this cycle.. vacation, audit at work and other things getting in the way.. I hope to return asap 14:08:02 Bug 17600, bug 27526, bug 17427 and bug 25078 14:08:03 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17600 enhancement, P5 - low, ---, jonathan.druart+koha, Needs Signoff , Standardize the EXPORT 14:08:03 similar, working through things, hope to have more time soon 14:08:04 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27526 enhancement, P5 - low, ---, jonathan.druart+koha, Needs Signoff , Remove Mod/AddItemFromMarc from additem.pl 14:08:05 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17427 normal, P5 - low, ---, jonathan.druart+koha, Needs Signoff , Replace CGI::Session with Data::Session 14:08:06 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25078 enhancement, P5 - low, ---, jonathan.druart+koha, Needs Signoff , Update DB process - wrap each DBRev inside a transaction and better error handling 14:08:19 I really would like some pair of eyes on them this week or next week, they are important moves and must be pushed ASAP. 14:08:20 ... but also little help with those apart from reminding devs 14:08:27 ASAP: in the next couple of weeks 14:08:45 any questions? 14:08:50 I'll make sure to include those in the next QA mail 14:09:45 Project Koha_Master_D9 build #1679: STILL UNSTABLE in 42 min: https://jenkins.koha-community.org/job/Koha_Master_D9/1679/ 14:09:54 :o 14:10:01 17427 won't be pushed in the next couple of week however, IMO we should wait a couple of months to not diverge too much too quickly with 21.05.x (CGI::Session vs Data::Session) 14:10:19 questions, actions, nothing? 14:11:07 I'm not sure 14:11:07 #topic Updates from the Release Maintainers 14:11:15 not sure about? 14:11:35 what actions can we do, or how we split in teams to tackle things 14:11:43 I'm waiting on 21.05.x pushes 14:11:50 20.05: handover done on old branch, handover received on new branch, first backports done. 14:12:04 tuxayo++ 14:12:09 Do we have security repo access? 14:12:26 Are Wainui and Aliesha happy with things now 14:13:00 ashimema: yes 14:13:12 You should be able to tell that from the git UI tuxayo 14:13:20 Brill, thanks Joubu 14:13:25 ashimema: thank, I'll check that out 14:13:26 when Kyle is back we will coordinate on pushing for 21.05, he has been on vacation 14:13:35 tuxayo: did you use the security repo last cycle? 14:13:36 oki no pb 14:13:40 tomorrow 14:13:49 Joubu: thankfully, nope :D 14:14:02 (fingercrossed) 14:14:34 nobody has push access apparently 14:14:36 You will this cycle.. I'm working on a few 14:14:45 drop me an email please, I will have a look tomorrow 14:14:45 ashimema: noooo 14:15:02 ok thanks 14:15:23 kidclamp: there are few 21.05 candidates (see the bz kw), don't forget them 14:15:23 Interesting 14:15:32 #topic Updates from the QA team 14:16:13 I am running behind, and I would like to rely stronly on the QA team for the next couple of week (/one month?) 14:16:22 please QA in conservative mode 14:16:46 No time for QA yet, still following up on ticket where I got answers, rebases, ect 14:17:09 ok 14:17:22 we'll try our best 14:17:42 nothing from QAers? 14:17:47 I mean, others? 14:18:01 I've been sending the welcome eamil and 2 more - we are already in week 3 14:18:17 So far this cycle is shaping up to be a busy one work wise for me.. just a warning there that I will try to QA but likely won't hit the flow I have been the last couple of cycles 14:18:17 shoutout to kidclamp who took quite a few bugs out of our list last week :) 14:18:47 I'll also remind more about "long sitting" bugs as i'd like to reduce the max time a bug sits in QA queue 14:18:59 yes, great QA run kidclamp, thanks! :) 14:19:11 priorites apply as usually of course - bugs before enh etc. 14:19:17 will try to keep up:-) 14:19:26 a lot of bugs are a bit "out of reach" for me these days 14:19:35 in terms of complexity 14:19:41 kidclamp++ 14:19:47 The recall one is tough, bug 19532 14:19:47 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19532 new feature, P1 - high, ---, aleisha, Signed Off , Recalls for Koha 14:19:59 but will try to remind and pick on the others whenever i can 14:20:29 if someone wants to team of up something - always happy to (like split GUI testing and technical) 14:20:40 I can't commit to the submitted recalls.. it would cause big issues here as it's not at all what we think of as recalls 14:20:55 i think the question is if it's just a name problem 14:21:32 if the featue is still useful, we shoudl consider it maybe 14:21:53 and talk about how to communicate the difference from a classical recall feature 14:21:58 bug 25260 could be a good team work for QA team members 14:21:58 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25260 enhancement, P5 - low, ---, tomascohen, Signed Off , Merge 'reserves' and 'old_reserves' into a new 'holds' table 14:22:29 I'd like to see that one in tcohen.. I thought it was waiting for a rebasr or other work or something 14:22:30 I hadn't noticed that it was recalls by patrons rather than the library 14:22:47 we need to sync and coordinate, or we won't finish anything (like the last cycle) 14:23:09 I am moving on 14:23:11 The logic is also somewhat weird/different henryb . Would love a librarians opinion for naming it 14:23:23 need to keep the meeting in its track 14:23:27 henryb: i think comments from a library might help get it moving 14:23:33 we could call them 'patron recalls' :-P 14:23:41 Joubu++ 14:23:43 to support companies: get customer feedback on it :) 14:23:51 patron driven recalls? 14:24:11 if we need a discussion, we should start it ASAP on the mailing list 14:24:26 action? 14:24:28 Moving on 14:24:36 #topic Status of roadmap projects 14:24:47 I selected a few 14:25:07 I sent an email to the workgroups for: 14:25:11 * Get rid of non-XSLT views 14:25:43 => We are going to remove the non-XSLT views even if not all features have been moved, unless someone is opposed to that 14:25:52 * Fix item visibility at the OPAC 14:25:53 Nice 14:25:58 => Waiting for answers 14:26:03 * Koha Cookbook Project 14:26:06 => No answer yet 14:26:16 * Accessibility Improvements 14:26:20 Henry is going to work on the bug listed 14:26:31 henryb: do you want to say something about it? 14:26:36 ++ 14:26:59 Excellent henryb, 14:27:02 The bugs are mostly small things like adding labels 14:27:13 I saw a lot of accessibility bugs move past - are those on the list? 14:27:23 "a small step for men ... 14:27:32 a lot has been pushed into 21.05 14:27:36 There's one to fix the colour contrast issues on the OPAC which again is probably lots of small tweaks 14:27:37 henryb++ small steps are good 14:27:59 they are not in 20.11.x to avoid to much backport job and translations 14:28:00 Wainui is working on some others too like adding legends to tables 14:28:09 (https://annuel.framapad.org/p/koha_21.11_roadmap < we are talking about that, but you all know that) 14:28:11 we had a question about this at the german user group meeting actually - so it seems there is definitely interest (contrast that is) 14:28:42 I think they all have the 'accessibility' keyword but they're not all listed on the roadmap document 14:29:17 That's it from me unless anyone has questions or ideas 14:30:06 https://bugs.koha-community.org/bugzilla3/buglist.cgi?cmdtype=dorem&list_id=372048&namedcmd=Accessibility&remaction=run&sharer_id=378 14:30:10 that's the list 14:30:28 thanks henryb, we will keep an eye on those bugs! 14:30:41 * Wiki migration 14:30:58 I sent en email and still waiting for more replies 14:30:59 We need to decide on the software (migrate to a newer version of mediawiki or switch to dokuwiki) 14:31:25 so either we restart the discussion on the general koha ML, or decide during a meeting? 14:31:27 Joubu: sitting on a draft repy for that 14:31:36 i think my main concern is moving from one wiki to another... 14:31:37 or we (the 4,5 members in the workgroup) decide? 14:31:41 I have been posting updates in the bug. 14:32:01 in terms of both requiring wiki snytax etc. so there won't be much innovation, it's more bug fixing 14:32:21 > I sent en email 14:32:21 Is it in the general list? There are thing in march 14:32:33 tuxayo: to the workgroup only 14:32:34 tuxayo: to everyone who signed up 14:32:37 for the topic 14:32:39 ok 14:33:03 no opinion? 14:33:11 mediawiki++ 14:33:12 thd: what's your opinion about this question? 14:33:19 i think dokuwiki woudl work well, but requires some changes 14:33:21 50% 50% for me 14:33:29 I have successfully tested excluding old content from simple search using the Vector skin. 14:34:05 I am open to either, but have basically no experience with doku 14:34:17 We have working code which I have posted for migrating the database and upgrading MediaWiki. 14:34:26 I am preparing another update. 14:34:38 ... to the code. 14:34:55 If we go the mediawiki route I do think we should add the editor 14:35:10 editor = more wysiqyg? 14:35:14 I favour MediaWiki over Dokuwiki for much better support for many issues. 14:35:18 Yup 14:35:29 Go play on Wikipedia.. it has the editor 14:35:29 i think they are really different "beasts" in some aspects 14:35:36 ashimema: is that the thing that requires another service running? i've stumbled upon that when trying to setup my own mediawiki 14:35:36 Very much wysiwyg 14:35:41 Yup 14:35:45 got no acount, but will try to look it up then 14:35:58 MediaWiki has the new VisualEditor extension. 14:36:08 i think a part of our issue is that it's not easy to sue right now, i am in favor of trying an editor if there is one 14:36:16 so that's a point for mediawiki then 14:36:27 there are visual editors for dokuwiki, but i never found one that really worked well 14:36:29 I've not used either much recently but did have experience with mediawiki for a few years 14:36:33 bah we code so we are not afraid of wiki syntax 14:36:36 especially if you switch modes 14:36:48 cait1: no need for an accoun to play with the sandbox to test things https://en.wikipedia.org/wiki/Wikipedia:Sandbox 14:36:56 thx tuxayo! 14:37:00 Yup 14:37:05 As a complete beginner, mediawiki looks nicer and easier to use 14:37:06 There is a years old bug that search by tag is broken in MediaWiki. 14:37:22 ok, so if we are leaning mediawiki 14:37:27 ooops 14:37:29 1) Figure out the update 14:37:36 There is a years old bug that search by tag is broken in Dokuwiki. 14:37:38 2) figure out a concept to mark outdated content for review? 14:37:56 Search by tag has always worked in MediaWiki. 14:38:03 thd: i think tagging is actually a plugin fature in dokuwiki 14:38:03 fridolin: «we code so we are not afraid of wiki syntax» a lot of stuff on the wiki is not only tech stuff 14:38:15 There are loads of templates available for mediawiki for maintainence making 14:38:19 indeed ;) 14:38:32 * cait1 waves at josef_moravec 14:38:45 Project Koha_Master build #1673: STILL UNSTABLE in 55 min: https://jenkins.koha-community.org/job/Koha_Master/1673/ 14:38:47 so maybe we should call a wiki meeting to make more precise plans? 14:38:54 ok, perfect then. We will list/prepare the next steps and will report at the next meeting 14:38:57 Do it 14:39:03 cait1: between us it good enough 14:39:05 :) 14:39:07 cait1: Yes, but the tag which at one time allowed searching by tag has been long broken in MediaWiki. 14:39:07 small groups 14:39:09 another plus for updating... user registration 14:39:31 i am not sure if dokuwiki has the review options (at least witout plugins) and user migration might have been a bit bad 14:39:37 yep, meant a meeting for the work group 14:39:52 I am moving on, we have a decision, more than I expected :) 14:39:57 * Bug 27829 - [OMNIBUS] Remove specific LANG installer data 14:39:57 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27829 enhancement, P5 - low, ---, koha-bugs, NEW , [OMNIBUS] Remove specific LANG installer data 14:40:02 thx Joubu 14:40:06 => Bernardo is working on creating a UNIMARC version for "en" that will be translatable via pootle. 14:40:15 We are certainly going to remove the specific fr-FR biblio frameworks. 14:40:18 bgkriegel++ 14:40:27 I will start the discussion with French (already started a bit) on the fr ML 14:40:34 I will create a patch for fr-CA and rebase nb-NO 14:40:38 bgkriegel++ 14:40:42 the goal is to have them all remove for 21.11 14:40:43 Joubu++ too 14:40:46 removed* 14:40:54 please have an eye on items - fr-FR has a lot less standard mappings 14:41:00 that's all for the topics I listed 14:41:04 That will be so great 14:41:08 might be nice to bring that up to date with MARC21 a bit more 14:41:25 cait1: Bernardo is doing a crazy work and is reviewing everything 14:41:29 wow 14:41:33 shoudl not have wondered about that :) 14:41:36 bgkriegel++ 14:41:59 move on? 14:42:02 and we trying to provide a UNIMARC framework as closed as possible from the.. 14:42:08 (cannot find the word) 14:42:13 standard/norm? 14:42:21 makes sense yes 14:42:24 UNIMARC standard 14:42:27 Excellent 14:42:58 fridolin: any french libraries interested? Is actually the default framework much used? 14:43:07 something else you would like to add about the roadmap topics? 14:43:17 just a Joubu++ 14:43:23 I will continue to send few more emails in the upcoming days 14:43:27 I disfavour a new wiki. 14:43:38 and... I will drop the topic if I don't get answers 14:43:44 thd: i think we have moved on from that 14:43:49 Ok. 14:43:58 but we still need to makr and review tons 14:44:04 thd: we can continue by email of a bit after the meeting 14:44:05 sorry i dont know 14:44:07 or* 14:44:19 Joubu: that's fair 14:44:25 #topic Actions from last meeting 14:44:29 postponing 14:44:33 (one more time) 14:44:47 #action ashimema Write a coding guideline to clarify our message types: 'alert' vs 'error' (context of bug 27695) - last postpone 14:44:47 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27695 minor, P5 - low, ---, oleonard, RESOLVED FIXED, Fix style of messages on Elasticsearch configuration page 14:44:57 #action kidclamp Ask the ML for additional info about how to implement opt-out for notices. One idea would be to have "My message" at the OPAC (last postpone) 14:44:59 We should add a standing agenda item: "Postpone actions" :P 14:45:12 bgkriegel++ Joubu++ great work on cleanup getting thing closer 14:45:18 #topic General development discussion (trends, ideas, ...) 14:45:22 (sorry, that's unfair of me to say as I don't have any) 14:45:23 Sooo 14:45:28 #topic How to handle command line options vs system preferences in cron jobs? 14:45:43 this one, I haven't prepared, but we need to trigger actions 14:45:56 that one was from me, i think i added bugs to agenda, sec 14:45:57 cait1: would you like to resume that please? 14:46:00 good question 14:46:02 Good topic 14:46:09 See Bug 28457 and Bug 25499 for recent discussion. And Bug 24968. 14:46:09 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28457 enhancement, P5 - low, ---, dcook, Needs Signoff , cleanup_database.pl self-registration options are not configurable 14:46:09 I propose using the 'configurations' table, to build a UI for managing cronjob default parameters 14:46:10 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25499 normal, P5 - low, ---, katrin.fischer, CLOSED FIXED, Fund code column is empty when closing a budget 14:46:11 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24968 enhancement, P5 - low, ---, koha-bugs, NEW , Add Syspref controls for cronjobs 14:46:26 tcohen: short term solution, not never implemented solution 14:46:49 yes please, we have really needed feature stuck right now 14:46:49 -.- 14:46:52 and we can migratie 14:46:55 really open to that 14:47:19 ok, so the idea is to move more control from Command line into the preferences/configuration GUI side 14:47:28 this is especially helpful when you run multiple instances 14:47:32 gives power to the libraries etc 14:47:42 and you don't have to write complicated crontabs... 14:47:45 I volunteer to write some configuration page for cronjob parameters 14:47:54 Excellent 14:47:58 i think we can do that and still have a discussion 14:48:00 I can test/qa 14:48:04 the issue right now is 2 sided I think 14:48:16 a) a new parameter for a database_cleanup.pl 14:48:16 - default params 14:48:20 - what to run 14:48:23 so something that hasn't existed before 14:48:45 at the moment we have instances where you enable the feature on CLI, but it's controlled by pref 14:48:58 do we want the CLI switch? do we need it? 14:49:09 CLI switches should be overrides 14:49:14 I thought we did.... because I am scared sometimes of things I can't control :) but i'd be open to not require 14:49:17 > more control from Command line into the preferences/configuration GUI side 14:49:17 ++ for overide 14:49:18 * tuxayo will need to take a look if they can put evil stuff in that. Muhaha 14:49:27 for test instances with prod DB 14:49:49 Be nice if we could spot such overrides and now it in the GUI 14:49:54 so say... deleting old label batches 14:50:11 as an option toe cleanup_database 14:50:12 Like we do for the vhost syspref ones 14:50:34 at the moment we'd add the "flag" to the conjob call 14:50:44 Indeed 14:50:46 and then have a pref tell how long they shoudl be kept 14:50:49 So very hard to see 14:50:51 what is the stuck one? 14:50:58 so it#s not really an override, it's more like an on off... 14:51:11 bug 25429 (not 25499) 14:51:11 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25429 enhancement, P5 - low, ---, kyle, Signed Off , Cleanup Database - remove resolved claims returned from db after X days 14:51:18 there are 2 bug i am fraid i got the wrong bug number once mor eon the wiki :( 14:51:22 ep that's the one 14:51:31 thx Joubu 14:51:42 and the other was self regs 14:51:51 bug 28457 14:51:51 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28457 enhancement, P5 - low, ---, dcook, Needs Signoff , cleanup_database.pl self-registration options are not configurable 14:52:09 I think those bugs should move forward and add option switches 14:52:13 so the question si: CLI additionally to pref for new ones? 14:52:21 or just pref and that will be enough to turn the "feature"on 14:52:26 because it will then fit with a central config 14:52:32 if the pref is empty, the fature is expected to be off 14:52:54 I think we need a standard options iterator in the scripts base class that would update a flag of were passed an override so we can thing that the option is being overridden at the flag level 14:53:09 if we solved that... 2) is trickier: moving CLI optiosn into GUI - because then you already have crons scheduled that might need to be redone/rewritten 14:53:36 so.. how to make it smooth for existing installations 14:53:59 just make the current behavior the default 14:54:05 you can't 14:54:09 cait1: warning in about page? Maybe something more visible 14:54:12 unless you can see what they scheduled for the instance 14:54:22 if they set dealy=10 for some option, you need the value 14:54:29 delay 14:54:37 that applies to this one instance... to rpefill the pref 14:54:40 not sure if that is possible 14:54:49 i saypref, but it could be a confguaration page of course 14:54:50 no 14:55:03 you will put some good default value for delay in the UI 14:55:16 and the configured cronjob will pass --dekay 10 14:55:27 and that option switch will have more precedence 14:55:46 Exactly 14:55:51 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25429#c35 14:55:51 04Bug 25429: enhancement, P5 - low, ---, kyle, Signed Off , Cleanup Database - remove resolved claims returned from db after X days 14:55:58 I would totally avoid sysprefs for this 14:55:58 Let flags passed take precedence. 14:56:01 > It means that you need to have a sysadmin change a cronjob for ALL instances 14:56:01 > if there's just 1 instance that wants to be able to use the system 14:56:02 > preference "CleanUpDatabaseReturnClaims". 14:56:05 (from David) 14:56:25 Record that precidence with each run of the script to mark it as being used in the gui 14:56:29 That's my feeling 14:56:49 Then the librarian can see it's getting overriden... And can ask support to remove that if they want to change it 14:57:16 > to mark it as being used in the gui 14:57:17 nice 14:57:26 I like using your configuration table tcohen 14:58:57 I don't understand how the GUI will answer ALL the needs. IIUC we need to let the sysop turn off the feature even if the pref is ON 14:58:59 I like that idea as well, ashimema (noticing on the UI that is being overridden) 14:59:30 BUT David does not like the idea to have a separate cronjob, if one library wants a feature and others don't 14:59:54 (It's very warm here so just ignore me if what I am saying does not make sense) 15:00:24 > we need to let the sysop turn off the feature even if the pref is ON 15:00:24 if the cron args have precedence so can it be used to disable also? 15:00:41 i think a default for deletes is a bad idea 15:00:46 in other cases it works of ocurse 15:00:59 but for deletes i'd rather have off as a default 15:01:42 actions? what do we do? 15:02:02 there is still a topic on the agenda 15:02:18 I volunteered to write something we can work on top 15:02:31 maybe also comment on th bugs 15:02:32 you are suggesting a whole new feature 15:02:40 hope we can unlock them 15:02:42 when need to unstuck the other bugs 15:02:51 logic and implementation beign 2 different things her ei think 15:03:08 first we need the logic... that can be moved to somehting nice 15:03:25 and for the bugs awaiting using the pattern/logic would be ok already 15:03:38 ok, 15:03:39 > default for deletes is a bad idea 15:03:40 Would there be a way to visibly show somewhere a list of important crons with 'sane' exampl defaults. To have a hope that at least basic personal data cleanup would done? 15:04:15 It's easy in the installer but what about existing installs? 15:05:39 I don't understand your questions 15:05:45 we need to move on anyway 15:05:54 please continue the discussion on the bug report 15:06:11 bug 25429 is where we discussed it 15:06:11 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25429 enhancement, P5 - low, ---, kyle, Signed Off , Cleanup Database - remove resolved claims returned from db after X days 15:06:11 ok 15:06:22