Time Nick Message
05:42 fridolin hi
05:42 wahanui kia ora, fridolin
06:06 magnuse \o/
06:13 calire morning
06:14 Oak Morning
06:19 ashimema Morning #koha
06:19 ashimema Nice to have you back Oak
06:19 ashimema rangi++ #historian
06:21 Oak ashimema you remember me! :) thank you!
06:22 ashimema I remember lots of people :)
06:22 ashimema I also had a near 2 year sabatical away from Koha so appreciated it when people remembered me when I came back ;)
06:23 ashimema #koha is such a lovely community :)
06:23 cait how could we forget? :)
06:43 marcelr hi #koha
06:44 gk I upgraded from 18.11.02 to 18.11.04.1, after upgrade and web installation I can login to staff client but OPAC throw errors like Can't use an undefined value as an ARRAY reference at /usr/lib/x86_64-linux-gnu/perl5/5.26/DBI.pm line 2081.
06:48 gk Hi koha how long one has to wait to be answered, in fact I am new to this.
06:48 ashimema Hi gk
06:48 ashimema lots of people are only just coming online this morning
06:49 ashimema We have a few customers running that particular version without issue..
06:49 ashimema What type of install are you using, Debian Packages (so you just did a apt update to upgrade) ?
06:50 gk hi ashimema I have installed on ubuntu 18.04
06:50 gk I did apt-get update & upgrade both went fine
06:51 gk Yes It is debian packages
06:52 ashimema mysql or mariadb and are you sure whichever it is is running?
06:52 gk It is mysql 5.7
06:52 ashimema initially I think I'd try a restart of all service in case something failed to restart during upgrade (it's a bit grabbing at straws, but worth a try)
06:53 ashimema I need to quickly grab some breakfast but will be back shortly
06:53 gk Its ok
06:59 magnuse Oak
07:00 gk Yes I did reboot my ubuntu server
07:00 alex_a bonjour
07:00 Oak magnuse
07:00 magnuse you gotta be quicker, Oak ;-)
07:01 magnuse gk: when do you get that error? just loking at the opac front page? or when searching?
07:02 gk When I search for something
07:03 Oak ashimema, you are awesome, as is everyone here. Yes, it's such a pleasant feeling to be remembered... especially when we've not met in person.
07:05 Oak Heh magnuse, was replying to a client. You know how one has to think hard about each sentence making sure it does not sound rude or abrupt.
07:14 magnuse Oak: yup, sure
07:15 magnuse kia ora paul_p and cait
07:17 Oak For g k's problem, I'm out of touch, but perhaps something to look at until someone can answer? https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16858
07:17 huginn` Bug 16858: major, P5 - low, ---, gmcharlt, RESOLVED DUPLICATE, import_borrowers.pl does not load because of mysql 5.7
07:21 mtj hi gk: try reindexing your records, if you have a search problem
07:21 gk hi mtji Yes I rebuild zebra searching works in staff window but not in OPAC
07:23 mtj gk hmm, ok.. thats a specifc problem...
07:24 gk yes mtj that is a specific problem do you need log info
07:24 * cait waves
07:27 * Oak waves back to cait
07:28 cait :)
07:30 mtj hiya cait, Oak
07:31 mtj gk, yes sure... http://paste.koha-community.org/
07:34 pastebot "gk" at 127.0.0.1 pasted "OPAC search error after upgrade" (10 lines) at http://paste.koha-community.org/2655
07:36 pastebot "gk" at 127.0.0.1 pasted "OPAC search error after upgrade" (10 lines) at http://paste.koha-community.org/2656
07:40 * andreashm waves
07:43 mtj gk, hmmm, looks like a 'tags' error? ... try setting your 'TagsEnabled' syspref to disable - and reload opac?
07:51 ashimema bug 21662 is back on the board for QA for anyone interested.. with a lovely followup thanks to Chris :)
07:51 huginn` Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21662 enhancement, P5 - low, 19.05, martin.renvoize, Signed Off , Missing developers from history
07:51 marcelr ashimema: today or tomorrow
07:52 ashimema :D
07:53 mtj hi ashimema, can i PM you re: release
07:53 ashimema sure
08:05 mtj Bug 21846 - Using emoji as tags doesn't discriminate between emoji when calculating weights or searching
08:05 huginn` Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21846 normal, P5 - low, ---, tomascohen, RESOLVED FIXED, Using emoji as tags doesn't discriminate between emoji when calculating weights or searching
08:06 mtj ^ ...hmm, i wonder if gk's error is caused by that patch, pushed to 18.11.04
08:06 ashimema @later tell oleonard any thoughts on how I can clarify the look on bug 21626 ?
08:06 huginn` ashimema: The operation succeeded.
08:07 ashimema hmm.. could be
08:08 ashimema gk there is a new release with a few more bugfixes coming out this afternoon btw.. just to gie you a heads up if you're doing upgrades at the minute
08:24 mtj gk.. did disabling the syspref fix you opac search error?
08:37 gk hi mtj
08:37 gk I disabled logs and the opac search works. Thank you very much. And tell me when should I enable it
09:04 gk ashimema, I will upgrade tomorrow. Thank you very much. Goodbye
09:09 josef_moravec hello #koha
09:09 magnuse hiya josef_moravec
09:10 josef_moravec hi magnuse
09:11 magnuse do we have any written guidelines for security? like "always protect against csrf"?
09:16 ashimema erm...
09:16 ashimema possibly
09:16 ashimema possibly not
09:20 josef_moravec hi ashimema: have you set date of release for 18.11.05?
09:20 ashimema today ;)
09:21 ashimema it's a security one so getting everyone together with all the bank holidays around the world this particular month has been.. interesting ;)
09:21 magnuse ashimema++
09:22 josef_moravec ashimema++
11:29 oleonard Hi all
11:34 josef_moravec hi oleonard
11:34 wahanui hi oleopard
11:34 magnuse ho oleonard
11:35 Oak Hi oleonard
11:35 wahanui hi oleopard
11:36 Oak ashimema++
11:42 magnuse has anyone ever had a third party do a security audit/assessment of koha, and published the results?
11:45 ashimema erm
11:46 ashimema not sure if the one's our customers have done are published per say.. they all get reported to the security section of BZ and fixed though..
11:48 magnuse i was thinking third party = someone who specialises in testing and looking for security problems
11:49 ashimema indeed
11:49 magnuse i had a couple of such audits on another project i was working on
11:49 ashimema we semi regularly have customers who hire external auditors and penetration testing companies to do a secuity audit for them
11:49 magnuse oh, cool!
11:50 magnuse and if they find anything it gets reported and fixed, of course?
11:50 magnuse otherwise there wouldn't be much point, i guess :-)
11:50 ashimema it's something I'd love to see more actively done within community though.. like a sponsored pot somewhere and a regular full on pen test done a month before each cycle's final release.. probably between feature freeze and release
11:50 ashimema yup
11:51 magnuse yeah, that would be awesome
11:51 * ashimema would also like to introduce arachni scanner into our jenkins workflow
11:51 ashimema but all these things need a bit of time and somone to host a system somewhere
11:51 magnuse i wonder if libraries and vendors would contribute to a fund for that
11:51 magnuse yeah, time...
11:52 ashimema I tried setting up arachni internally for a while.. but it turned out to be pretty heavy.. automatically trying to hack a system is actually pretty load intensive on the system your hitting ;)
11:52 ashimema it's one of the things I was hoping to discuss with koha-us.org actually ;)
11:53 ashimema might be right up their street as a non-profit and give them a bit of presence
11:53 * ashimema makes note to catch Todd
11:53 magnuse sounds like a good plan!
11:56 magnuse it would also be super cool if libraries that do audits could inform the community a bit about it, like sending an email to the list saying e.g. "we had an audit, found 5 problems and they have all been submitted as bz bugs"
11:56 magnuse and maybe say what the bugs were, once they have been fixed
11:59 magnuse and if the formal documentation from the testing could be made available (after the bugs have been fixed) that would of course also be awesome
12:02 * ashimema savours the moment of being top of the QA leaderboard for the month for the brief time before cait kicks be back down again :)
12:03 magnuse ashimema++
12:03 ashimema security bugs are made public on release I think aren't they
12:03 ashimema on bz I mean
12:03 magnuse looks like arachni has not been updated for a couple years?
12:03 ashimema It's not something I've really considered
12:04 ashimema lol.. it was a couple of years ago I looked at arachni
12:04 ashimema perhaps there's a better alternative these days
12:04 magnuse yeah, i think that is the way of security bugs
12:04 * magnuse dunno
12:05 magnuse maybe i should send an email to the list and ask if anyone can disclose anything about security audits
12:06 ashimema looks like there was activity on it up to late september 2018.. but it wasn't released
12:07 magnuse oops
12:08 magnuse but without getting lost in particulars, yes it would be cool to have a small army of tools like that and unleash it on koha every now and then
12:08 magnuse also if there are any automated tools for things like accessibility
12:43 caroline_catlady good morning!
12:45 oleonard Hi caroline_catlady
12:50 cait ashimema: heh - i will push you down again ;)
12:57 ere Hi #koha!
12:58 ere Is this a spurious error from qa-test-tools or am I missing something:
12:58 ere missing_filter at line 12 ([% WHILE ( part_numbers.$i.defined || part_names.$i.defined ) %])
12:59 ere $i is just:
12:59 ere [% i = 0 %]
13:05 ashimema hmm.. feels spurious to me
13:05 oleonard It looks like a false alarm to me ere
13:12 ere thanks, I'll file an issue and ignore it for now :)
13:13 ashimema ta
13:17 lukeG ashimema++
13:20 ere ashimema: https://gitlab.com/koha-community/qa-test-tools/issues/17
13:41 m23 hello Koha
13:42 kidclamp push him around now cait, before he is the RM and pushes back
13:43 ashimema oh, bugzila graph colours changed with the update
13:44 oleonard Bugzilla got an update?
13:44 ashimema 'Needs signoff' went from orange to green
13:44 ashimema yeah, rangi did one last night I think.. twas only a minor one I think
13:45 * ashimema got all excited thinking his bug tree had suddenly got lots of attention
13:45 ashimema but alas the status's hadn't actually changed
13:45 m23 Is here any Kohadevbox guru? I'm not able to come Kohadevbox to life on one of my computer. Only on this machine a everytime get error: TASK [Update apt cache if needed] ********************************************** fatal: [stretch]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ", "unreachable": true} on start. Anybody saw this before? In my others 2 machines Kohadevbox running great without this isssue.
13:47 oleonard ashimema: Check it out, mine looks like a battleship https://bugs.koha-community.org/bugzilla3/data/webdot/ZpRP_OJlZ0.png
13:47 ashimema oh wow..
13:47 oleonard (Bug 14546)
13:47 huginn` Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14546 new feature, P5 - low, ---, oleonard, NEW , Make staff client templates responsive
13:47 ashimema m23 are you trying to use elastic?
13:48 ashimema a very recent change by oracle means kohadevbox won't build with elastic support at the minute..
13:48 m23 ashimema No. I know about "proglem Oracle" :-)
13:48 ashimema oracle went then blew away the java package repository
13:48 huginn` News from kohagit: Bug 22692: (RM follow-up) Adjust test count <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=05f22c2159f3edf597d82ff76ea266760a7498cd>
13:48 huginn` News from kohagit: Bug 22478: (QA follow-up) Update tests to check for any script tags <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=d9b3b90849fd95d296b73b330c4e32ff018c81a5>
13:48 huginn` News from kohagit: Bug 22478: (QA follow-up) Make test consistent with variable name <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=d5e7dd15fc9c064f99739b27e5b40456b359f420>
13:48 huginn` News from kohagit: Bug 22478: (RMaint follow-up) source t::lib::Mocks <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=0fb9b9fdb080dfe8c7bccd7f83a9c63bb3c9b104>
13:48 huginn` News from kohagit: Bug 22478: (QA follow-up) Handle category in opac-shelves like a boolean <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=375dd35d5354d46c4c16f534494b123ce370c3f4>
13:48 huginn` News from kohagit: Bug 22692: Check for patron using cardnumber and userid <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=456a7ae6d452a4a805b521f0123c666bb8e84085>
13:48 huginn` News from kohagit: Bug 22692: Unit tests <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=30de51fa0c707322ce95a318df72ec5d7b5d3eb0>
13:48 huginn` News from kohagit: Bug 22478: Fix POD <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=401e8e791e32008e93e959dd9ed1b4491cb0796a>
13:48 huginn` News from kohagit: Bug 22542: Force back button to display personal data <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=6a0246e24838cfba672baf4aef080588b7d091bf>
13:48 huginn` News from kohagit: Bug 22478: Add tests <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=3b12416dc8d8f833bc745402ae835cc56c897fef>
13:48 huginn` News from kohagit: Bug 22478: Prevent XSS vulnerabilities when pagination appears <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=f021ca30a5d3944a43b4f6e089b21cfd9dc02997>
13:48 ashimema ah.. ok
13:48 ashimema no idea then I'm afraid :(
13:48 m23 "problem Oracle"
13:56 koha-jenkins Project Koha_18.11_D9 build #79: SUCCESS in 26 min: https://jenkins.koha-community.org/job/Koha_18.11_D9/79/
14:06 koha-jenkins Project Koha_18.11_U18 build #73: SUCCESS in 35 min: https://jenkins.koha-community.org/job/Koha_18.11_U18/73/
14:09 koha-jenkins Project Koha_18.11_D8 build #77: SUCCESS in 39 min: https://jenkins.koha-community.org/job/Koha_18.11_D8/77/
14:15 cait m23: try to turn elasticsesarchof in your config
14:15 cait destroy and start over
14:16 cait rangi said you can't install with elastic right now, missing ppa
14:16 m23 cait Already tried. Destroyed, ES off. But no luck :-(
14:17 cait :(
14:21 m23 cait It's some problem with ssh keys for access to devbox.
14:24 koha-jenkins Project Koha_Master_D9 build #721: SUCCESS in 28 min: https://jenkins.koha-community.org/job/Koha_Master_D9/721/
14:33 ashimema caroline_catlady: around?
14:33 caroline_catlady hi!
14:33 ashimema :)
14:33 cait ashimema++
14:34 ashimema just been running an idea around for a new page on k-c.org and wanted to run the content past you (and wizzyrea once she's about)
14:34 cait caroline_catlady: caramelized brown bread icecream.
14:34 ashimema https://mensuel.framapad.org/p/SlwLSSje2d
14:34 cait suffer with me :)
14:34 caroline_catlady hehe! I have no idea what caramelized brown bread is
14:34 cait i don't have either... but I want to find out!
14:35 ashimema it's a response to marcelr's comment on bug 21626
14:35 cait ashimema++
14:35 huginn` Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21626 enhancement, P5 - low, 19.05, martin.renvoize, Needs Signoff , Add 'current maintenance team' to the 'Koha team' page
14:35 cait # both slip patches!
14:35 ashimema does sound like amazing grub
14:35 caroline_catlady In my mind it's something like toasted whole wheat bread with honey on top
14:35 ashimema icecream obsessed.. you'll go far here... hehe
14:36 caroline_catlady ashimema: what # is marcelr's comment?
14:37 ashimema has you seen the bug?
14:37 caroline_catlady I haven't applied the patch, but I can take a look
14:37 ashimema there's screenshots on it ;)
14:38 caroline_catlady (better than trying to figure out wth is going on with ebbok lending ugh -_-)
14:38 ashimema https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=88885
14:38 ashimema basically, I put two teams next to each other.. the 'current maintanence team' on the right with the 'version release team' on the left
14:39 ashimema marcelr found it confusing listing two..
14:40 ashimema so far the best solution I've come up with is to either add a small description as to the two teams roles on that page.. or link out to the community wbsite page containing such a description of the two teams listed
14:41 caroline_catlady So right now, what is shown, the left column?
14:42 caroline_catlady I think what is confusing in the sreenshot is that the names are the same, so it's not clear what is what
14:42 ashimema right now.. as in without the patches at all?
14:42 caroline_catlady yes
14:42 koha-jenkins Project Koha_Master_U18 build #216: SUCCESS in 36 min: https://jenkins.koha-community.org/job/Koha_Master_U18/216/
14:43 ashimema without the patches at all what you see on the about page is just one team.. the one that was responsible during the initial development of that particular koha version
14:43 caroline_catlady the maintenance team should be only release maintainers?
14:43 ashimema no mention of whose maintaining it 'now'
14:43 caroline_catlady like release manager should not be in current maintenance team, no?
14:44 ashimema I think it's the whole team.. SO/QA and RM all have to work through the bugs before they hit the RMaints
14:44 ashimema that screenshot isn't great as it has the same team for both.. I only just noticed that
14:44 ashimema in reality there's overlap but usually the actual teams are fairly distinct
14:46 ashimema very occasionally a bug is only in a maint version so it doesn't hit the RM.. but in my experience so far that is rare.. more commonly the fix goes into master and then gets ported backwards by the rmaints
14:46 caroline_catlady ok
14:47 ashimema maybe it's just me who always found it confusing that the about page lists a team of people who are often not responsible at all for the koha you're running now..
14:47 caroline_catlady So the left column is the people who worked on the version the user is using, and the right column is the people working on the next version?
14:47 ashimema to me.. it's almost more helpful to know who the current maintenance team as it gives you people to approach for help.. for example
14:48 ashimema yeah.. that's pretty much it
14:48 caroline_catlady I like the idea of showcasing both teams
14:49 alreadygone oleonard, want me to help you with 14546
14:50 caroline_catlady But I would maybe change the list (release maintainers only in current maintenance team for example)
14:50 caroline_catlady And I think a mini paragraph explaining what each team does would be good for people who have no idea what release team and maintenance team do
14:50 koha-jenkins Project Koha_Master_D8 build #230: SUCCESS in 41 min: https://jenkins.koha-community.org/job/Koha_Master_D8/230/
14:51 oleonard Oak, of course you're welcome to submit patches. What do you have in mind?
14:52 caroline_catlady what do you think?
14:52 * ashimema is thinking
14:53 ashimema I think that screenshot it outdated.. I'm sure I've split the teams more nicely since
14:53 * ashimema is just checking that
14:53 caroline_catlady Il try applying the patch
14:54 Oak I'd love to incorporate CSS Grid where possible. So to decrease dependency on any 3rd party 'framework'.
14:55 oleonard Oak: That's contrary to the direction we've been going... We're using Bootstrap in both OPAC and staff client.
14:56 Oak Well. Okay.
14:56 Oak Bootstrap 4 then. I can help with migration if we are not on it already.
14:58 oleonard Bug 20168
14:58 huginn` Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20168 enhancement, P5 - low, ---, oleonard, NEW , Update of the OPAC bootstrap template to bootstrap v4
14:58 oleonard it looked like someone was going to take that on, but there hasn't been any word since
14:59 oleonard Oak is there a reason you want to avoid frameworks?
15:00 Oak Case in point: the _insert_name_here_ needs to be upgraded to version x of the framework.
15:00 caroline_catlady ugh, I think it's been too long since I applied bz patches
15:00 Oak Whereas, standards are forever :)
15:00 Oak But, no need to make drastic changes. Bootstrap upgrade is not that hard.
15:01 oleonard They're not forever. Table layout got upgraded to CSS layout with floats. CSS layout with floats will get upgraded to flexbox or grids
15:01 pastebot "caroline_catlady" at 127.0.0.1 pasted "I did git bz apply 21626 and it gave me" (14 lines) at http://paste.koha-community.org/2657
15:01 ashimema ooh. fun
15:01 ashimema not seen that before
15:01 ashimema let me clean it up a bit more first caroline_catlady
15:02 caroline_catlady ok thx
15:02 ashimema looks like some of the distinctions between teams have got lost during rebases
15:03 ashimema but either way.. do you think it's a good idea to have a description of how the release teams work on the main website?
15:03 caroline_catlady Not sure, I think I would just put it there (in the about section) and we already have a section on who does what and the cycle I think
15:04 ashimema okies, thanks :)
15:07 * oleonard is very frustrated that this page implies the plugin can do something it can't. http://multiple-select.wenzhixin.net.cn/getting-started/
15:07 oleonard ..specifically... using json as a datasource doesn't work
15:07 * oleonard is just complaining
15:09 cait where is the error in the last mail to the mailing list?
15:10 oleonard Good question
15:14 cait just checking... so it's not me :)
15:21 Oak I meant in the sense, these properties don't disappear... mostly; they are supported by browsers. Just that better ones get added to simplify doing things. Like floats are not gone. We still use floats in places, we just don't use them for layouts anymore. And there are no security concerns associates with it.
15:21 Oak However,
15:23 Oak I'm not sure if it'll be a good idea to expect from patrons to have an upgraded browser to support modern code.
15:23 Oak Bootstrap is just CSS too. And sure it takes care of lots of browser quirks.
15:24 Oak So I take back my silly comment.
15:35 caroline_catlady cait, did you ever asked around re: bug 21270 ?
15:35 huginn` Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21270 minor, P5 - low, ---, philippe.blouin, In Discussion , Not finding what you're looking for displaying uselessly
15:36 cait caroline_catlady: i think that one slipped through :(
15:36 cait or more i did but got no replies ont hat bu
15:36 cait g
15:37 caroline_catlady I stumbled upon it because a client had the problem
15:37 caroline_catlady they had ill turned on, but anonymous suggestions turned off and there was no link...
15:57 ashimema https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=89253
15:57 ashimema is that clearer caroline , cait ?
15:58 cait Koah not koha :)
15:59 cait and maintenance
15:59 cait heh
15:59 cait of your currently installed Koha version maybe?
15:59 cait otherwise yep
16:00 ashimema it's also re-ordered the members of the teams beneath the titles
16:00 ashimema did you spot that..
16:01 ashimema like the 'current maintanence team' now display your rmaint at the top instead of the rm and only displays the one relevant to your version.. not the other current ones
16:01 ashimema does that seem reasonable
16:01 cait hm why is translation manager missing?
16:01 ashimema and.. thanks for the spelling fixes
16:01 cait on the right
16:01 ashimema good question.. I may have missed it in the template
16:02 ashimema oh.. not template then.. source data
16:02 cait i like the maintainers
16:02 cait but maybe we shoudl list the version somewhere to make it clearer?
16:03 caroline_catlady I like
16:03 ashimema I also think it's worth adding dates to the current maintanence team
16:04 cait i wonder if we shoudl list all maints on top
16:04 caroline_catlady fix capitalization? Documentation Team -> Documentation team
16:04 ashimema :)
16:04 cait same for manager
16:04 ashimema oh.. that came from the original templates :)
16:04 caroline_catlady sorry!
16:04 ashimema but nows as good a time as any to fix that
16:04 ashimema no.. all good :)
16:05 caroline_catlady the source is the wiki?
16:05 ashimema for the teams.. now that's complicated ;)
16:06 caroline_catlady I like things alphabetized, but if the source is not alphabetized don't worry about it
16:06 ashimema the koha-community release notes pages, release notes in the installs, wiki pages and release-tools repository which contains a list too... they ALL dissagree with each other
16:06 caroline_catlady eesh
16:06 ashimema indeed
16:07 ashimema role or name alphabetized
16:07 ashimema I think the roles were in a particular order deliberately
16:07 caroline_catlady last name alphabetized within a role
16:07 ashimema names I'd be happy to sort
16:07 ashimema :)
16:07 cait translations
16:07 cait name sorting works
16:07 cait role sorting not :)
16:07 * ashimema needs to write notes for all this feedback somewhere.. he needs to scarper to be a cub leader shortly
16:07 cait so a sensible order is nice without a-z
16:08 cait taking my tired brain home - talk to you all later
16:09 caroline_catlady good luck with the cubs!
16:09 ashimema ta :)
16:09 caroline_catlady ashimema: want me to add the feedback as a comment?
16:09 caroline_catlady in the bug
16:09 ashimema litter picking and geocaching tonight
16:09 ashimema i'm sure they'll enjoy it
16:09 caroline_catlady nice!
16:09 ashimema that would be great.. then I can make sure I do it all
16:10 caroline_catlady ok!
16:13 * ashimema runs off.. thanks guys :)
19:53 rangi morning
19:54 cait morning
19:56 caroline_catlady morning rangi!
19:57 rangi hey caroline_catlady :)
19:58 cait caroline_catlady is to blame for me thinking about icecream all day long!
20:01 rangi heh
20:01 ashimema Haha
20:02 ashimema Morning rangi
20:02 ashimema Evening other hemisphere
20:02 rangi heh
20:02 caroline_catlady I'm suffering too ;)
20:02 * caroline_catlady found out what caramelized brown bread was
20:03 caroline_catlady anything caramelized is bound to be delicious
20:05 cait that's a good rule
20:05 cait add a little salt... heavenyl
20:08 * ashimema salivates
20:12 * andreashm just logged on. interesting first line =)
20:12 caroline_catlady XD
20:18 cait :)
20:18 ashimema Lol
20:18 ashimema Hope we didn't scare Oak away
20:19 cait why?
20:19 cait with icecream?
20:19 ashimema Hehe
21:28 caroline_catlady good night everyone!
23:53 lavamind I learned this week that our academic library will be switching to Koha! (from an old version of Symphony)
23:54 lavamind migration project is launching in 2 weeks