Evergreen ILS Website

IRC log for #evergreen, 2017-09-07

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
00:18 remingtron_ joined #evergreen
04:32 pinesol_green News from qatests: Test Success <http://testing.evergreen-ils.org/~live>
05:10 rlefaive joined #evergreen
06:01 rlefaive joined #evergreen
06:24 rlefaive joined #evergreen
07:10 rjackson_isl joined #evergreen
07:33 dwgreen joined #evergreen
08:18 collum joined #evergreen
08:41 mmorgan joined #evergreen
08:46 _adb joined #evergreen
08:54 Dyrcona joined #evergreen
08:59 kmlussier joined #evergreen
09:04 rkw joined #evergreen
09:05 jvwoolf joined #evergreen
09:10 jvwoolf1 joined #evergreen
09:10 jvwoolf1 left #evergreen
09:27 yboston joined #evergreen
09:28 gmcharlt we'll be taking webby.evergreencatalog.com down now for updates and upgrading it to 3.0-beta
09:28 gmcharlt it will be back up later this afternoon
09:28 kmlussier gmcharlt++
09:31 kmlussier dbs: Yesterday, I started setting up an Evergreen YouTube account, which is linked to the Google Evergreen brand account you created.
09:32 kmlussier dbs: It looks like the account owner is the only person who can add other managers to the YouTube account. Would you be able to add rhamby_ as an manager?
09:33 rkw Is this the correct channel to get help installing a new Evergreen server?
09:34 kmlussier rkw: Yes, it is!
09:36 rkw thanks kmlussier! I'm installing EG 2.12.5, following the instructions from https://evergreen-ils.org/documentat​ion/install/README_2_12.html#_config​uration_and_compilation_instructions
09:36 pinesol_green [evergreen|Mike Rylander] Proposed 2.12.5-3.0 upgrade SQL - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=5b5c81f>
09:36 pinesol_green [evergreen|Mike Rylander] Incorporate view update from LP#1714589 - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=1eb33ec>
09:37 rkw at Item #5, configure succeeds, but 'make' fails with:   /usr/bin/ld: cannot find -ldbdpgsql     ld returned 1 exit status
09:38 jvwoolf joined #evergreen
09:38 rkw is anyone familiar with this error?
09:39 rhamby_ kmlussier: (other web team) I just realized that the connect section of the involvement page doesn' thave our facebook or twitter info so adding that real quick
09:39 kmlussier rhamby_: Great, thanks!
09:39 kmlussier rhamby++
09:42 dbwells rkw: Yes, we've seen that error.  It can have a number of causes, unfortunately.  What OS distribution are you on?
09:42 rkw ubuntu trusty
09:42 cesardv rkw: yep I've seen that being caused by perl and related dependencies being slightly older than required by Evergreen (on wheeze at least) check you perl versions
09:43 rkw cesardv: ok, will do. thanks
09:43 dbwells rkw: Any chance you are running 32-bit?  We need to tweak the configure line on our one lonely 32-bit install.
09:44 Dyrcona rkw: IIRC, that is not Perl. It's not finding the C libdbdpgsql libraries, and on 14.04, that's not usually an issue, except possibly as csharp says, on 32-bit.
09:44 Dyrcona Sorry, dbwells... :)
09:45 Dyrcona dbwells++
09:45 * Dyrcona is doing too many things at once, resumes lurking.
09:45 rkw dbwells: I am running 32 bit .... I could do 64, but chose 32 for some unknown reason
09:46 rkw dbwells: is it better to choose 'server' over 'desktop' iso?
09:48 dbwells rkw: 32-bit is okay, you just need to find libdbdpgsql.so.  On my 32-bit system it is in /usr/lib/i386-linux-gnu/dbd/
09:48 Dyrcona rkw: Use the 64-bit server ISO, always.
09:48 rkw dyrcona: ok, downloading it now....will be awhile
09:49 dbwells rkw: I agree with Dyrcona's advice as the long-term solution, but if you just want to get it running ASAP, 32-bit isn't a big obstacle.
09:49 rkw dbwells: I'd like to continue installing on my 32 bit server OS .... if only for the experience, so I will continue to try to resolve this on 32bit
09:50 rkw dbwells: I have the libdbdpgsql.so in the same dir on my system
09:51 dbwells rkw: Alright, you are probably close.  Try adding --with-dbi=/usr/lib/i386-linux-gnu/dbd/ to your configure command, then see if make is more happy.
09:51 rkw dbwells: will do, thank you
09:51 Dyrcona yeah, that looks right.
09:52 Dyrcona Been a long time since I tried 32-bit and that was just to see if it would install.
09:53 rkw Dyrcona: I'm new enough that the install experience will help, so like you, I just want to see if I can do 32-bit while the 64-bit downloads
09:55 Dyrcona Last time I had a library issue, I just munged the makefiles.
09:55 dbwells In my case, I fired up an older server a few months ago in laziness to do a test install, had no recollection it was 32-bit, then was majorly confused for longer than I care to admit :)
09:57 Dyrcona I haven't installed on 14.04 for a while, either, for that matter. I'm mostly using Ubuntu 16.04 and Debian 8.
09:58 pinesol_green [evergreen|Galen Charlton] start work on 3.0 release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=2da1e4f>
09:58 pinesol_green [evergreen|Galen Charlton] add organizations who sponsored develpoment written by Equinox - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=fa4fe4f>
09:58 pinesol_green [evergreen|Jane Sandberg] Docs: copy-editing 3.0 release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=2d53e56>
09:58 pinesol_green [evergreen|Dan Wells] Slightly rename release notes to follow existing convention - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=6cf84d5>
09:58 pinesol_green [evergreen|Dan Wells] Fix thinko in 3.0 release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=bf55771>
10:00 rkw dbwells: Dyrcona: make is happy ... moving on. Thank you!
10:00 dbwells rkw: Great, glad to help.  Good luck!
10:01 kmlussier dbwells++ Dyrcona++
10:08 dbs kmlussier: sure thing
10:09 dbs kmlussier: done
10:10 kmlussier dbs++
10:17 collum_ joined #evergreen
10:26 pinesol_green [evergreen|Dan Wells] Clean up RELEASE_NOTES_NEXT - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=5468dc3>
10:30 rhamby_ dbs++
11:22 Bmagic dbs++ #cause it's trending
11:25 Dyrcona Does bug 1703411 really affect Evergreen, too? I would think it pretty much only affects OpenSRF since that handles the XMPP layer.
11:25 pinesol_green Launchpad bug 1703411 in OpenSRF "OpenSRF: XMPP Non-SASL auth is being phased out" [Undecided,New] https://launchpad.net/bugs/1703411
11:27 miker Dyrcona: yeah, it's just opensrf, really.  I'm looking at that, too :)
11:28 Dyrcona I was just looking at different SASL implementations, just scanning the docs and checking licenses.
11:29 abneiman miker / Dyrcona : I switched it from EG to OpenSRF but wasn't sure if it should stay in EG as well
11:30 Dyrcona abneiman++ # I noticed that. I probably would have forgotten this bug if you hadn't done that. :)
11:31 dbs Bmagic: haha :)
11:31 Dyrcona Not that I'm expecting to fix it, but you never know....
11:31 dbs Bmagic++
11:31 Bmagic haha
11:34 * dbs notes that none of the sample catalogues shared so far redirect to HTTPS :/
11:35 Dyrcona Not everything needs to be encrypted. I know it makes us feel warm and fuzzy, but....
11:35 dbs Oh wait the Czechs did, yay
11:36 dbs I strongly dislike having usernames and passwords being sent in plain text. I don't think that's a warm and fuzzy concern.
11:36 Dyrcona Authentication should be encrypted, and in Evergreen it is.
11:37 Dyrcona Just quickly doing a search without logging in? Not so much.
11:37 Dyrcona And, there's no reason to encrypt sites like my personal site, at all.
11:38 Dyrcona Encrypt your email, first, then I'll take HTTPS everywhere seriously. :P
11:39 dbs Good point on the auth redirect!
11:39 dbs dbs--
11:39 Bmagic dbs++
11:40 Dyrcona dbs++ # To counterbalance his silly self-decrementation. :)
11:40 dbs Still, if you have certs already to support HTTPS auth, why not make the whole site HTTPS?
11:40 dwgreen LetsEncrypt it. :)
11:40 berick and it's also about talking to who you think you are talking to
11:40 berick regardless of encryption
11:40 Bmagic dbs: it's because of the handshake overhead, duh!
11:40 dwgreen Probably would help with those scripts that can only be served over https too
11:40 Bmagic 56k can't handle the truth!
11:41 dwgreen External scripts I mean
11:41 berick Bmagic: heh
11:41 Dyrcona ha! For trusting who you are talking to, self-signed certs are safer, if you very the certs.
11:41 Dyrcona s/very/verify/
11:41 Dyrcona I'm supposed to trust the CIA to sign certs? :)
11:42 Bmagic HTTP specification headers need to be changed to include a "dial-up" flag T/F
11:42 dbs nginx + http2 makes TLS negotiation even less of an issue
11:42 * Dyrcona has considered creating a browser called Paranoia that doesn't have any trusted authorities, remembers certs per domain, and tracks them.
11:43 dbs (well, http2 really, nginx just does a nice job of making it easy)
11:43 Bmagic Dyrcona: Just use IE if you want everything to be broken
11:43 Dyrcona Bmagic: Have a look at the authorities that your browser trusts some time. You might be a little surprised.
11:43 jonadab Dyrcona: You mean like the way ssh uses certs?  Assume that in practice, attacks are very unlikely to happen the _first_ time you visit a site?
11:44 Bmagic I've looked and I have been surprised!
11:44 jonadab But if the cert changes, that's a cause for alarm no matter who signed it?
11:44 jonadab And yes, the list of what authorities the major browsers trust is ridiculous.
11:46 Dyrcona jonadab: It depends on the sites you're visiting and why.
11:46 dbs dwgreen: We're using LetsEncrypt on almost everything except our EG instance, which has a wildcard from 2015 that expires next year... just in time for LE to start issuing wildcard certs
11:46 Dyrcona There have been cases of spoofed Microsoft certs in the wild being used in attacks.
11:47 * dbs heads off to a meeting
11:47 dwgreen dbs: I have been keeping an eye on LE's wildcard certificates. We have close to 50 EZproxy instances we manage, and they would be perfect for the job... except I think LE plans to only make them for the apex domain, which won't work for us.
11:48 dbs dwgreen: oh yeah, EZproxy is our other one!
11:48 * dbs really out now
11:48 Bmagic We switched to letsencrypt for EG, but we recently hit the ceiling for number of domains allowed to have letsencrypt (30). And instead of jumping through more hoops to get around that limit, we bought a wildcard
11:49 * Dyrcona has experimented with creating an authority and signing his own certs. I trust myself more than anyone else. :)
11:51 Dyrcona Fun thing about running your own authority, is you can sign user certs and allow access only to holders of those specific certs or certs signed by your authority.
11:52 dwgreen Bmagic: Was that with using SAN certificates or just 30 different subdomain/certs?
11:55 Bmagic I believe it was 30 different certs associated with one email
11:55 Bmagic but SAN was a way around that
12:08 jihpringle joined #evergreen
12:19 pinesol_green [evergreen|Jane Sandberg] Docs: updates to Added Content instructions - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=81201ca>
12:26 Dyrcona hmm.
12:26 * Dyrcona thought he saw port 7680 in the websockets config the other day.
12:26 * Dyrcona musta been hallucinating.
12:36 Dyrcona Weird. It is there.
12:37 * Dyrcona checks git log.
12:38 Dyrcona Ah ha. Got it.
12:39 Dyrcona My apache2.conf predates 2fc52cfa
12:39 pinesol_green Dyrcona: [opensrf|Bill Erickson] LP#1667091 Remove non-SSL websockets sample configs - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=2fc52cf>
12:57 pinesol_green [evergreen|Jane Sandberg] Docs: updates to My Lists in patron account docs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=3f7c6e5>
12:57 pinesol_green [evergreen|Jane Sandberg] Docs: making support scripts adoc formatting more consistent, adding marc stream importer docs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=0e99828>
13:16 kmlussier OK, Evergreen YouTube channel is all set up! I'm hoping you all subscribe! https://www.youtube.com/chan​nel/UC83L8WyXoj8Kf9hShdDY61A
13:17 kmlussier Not only so that you can be updated when new videos are posted, but also so that we can reach 100 subscribers to get a custom URL.
13:18 Bmagic kmlussier++
13:18 Bmagic "I love videos"
13:18 Dyrcona kmlussier++
13:26 rjackson_isl kmlussier++
13:26 csharp I'm working on sussing out an issue we're the PO JEDI A/T events are erroring out with 'Can't call method "class_name" on an undefined value at /usr/local/share/perl/5.18.2/Open​ILS/Application/Trigger/Event.pm line 594.'
13:27 Dyrcona busted/out of date IDL?
13:28 csharp oh
13:28 csharp hmm
13:28 csharp there's a thought - I'll have to rule that out
13:28 csharp line 594 is my $fhint = OpenILS::Application->publish_fieldmapper->{​$context->class_name}{links}{$step}{class};
13:29 csharp and I created some debugging to output the value of $context as it runs and got https://pastebin.com/CHpP91fn\
13:29 * csharp runs off to check IDL
13:37 csharp IDL looks ok
13:38 csharp now checking the environment for the event def
13:40 csharp no changes to environment between 2.11.1 and 2.12.4
13:40 csharp did anything about a/t change?
13:47 pinesol_green [evergreen|Jane Sandberg] Docs: adding to the patron myopac holds/circ history docs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=f51917d>
13:47 Dyrcona Well, none of those contexts look like undefined values in your paste, if that is indeed the $context.
13:48 csharp there are two lines that end with "$context ="
13:48 csharp visible in https://pastebin.com/raw/CHpP91fn
13:50 ohiojoe DIG meeting in about 10 minutes, just an fyi
13:52 Dyrcona csharp: I missed those in the non-raw version. Those are likely your culprits. Unfortunately, I don't know what would cause that to happen.
13:54 Dyrcona I'd have a look at what's going on with the data for those purchase orders. It very well may be missing copies or something like that.
13:54 rlefaive_ joined #evergreen
13:55 csharp it's *all* POs that are failing so it looks like a structural problem
13:57 kmlussier joined #evergreen
14:01 ohiojoe ready?  let's do this
14:01 ohiojoe #startmeeting 2017-09-07 Documentation Interest Group Meeting
14:01 pinesol_green Meeting started Thu Sep  7 14:01:44 2017 US/Eastern.  The chair is ohiojoe. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01 pinesol_green The meeting name has been set to '2017_09_07_documentation_interest_group_meeting'
14:01 ohiojoe please introduce yourselves, paste "#info <username> is <name> <affiliation>" to identify who you are and what organization, if any, you represent
14:02 BAM_ joined #evergreen
14:02 sandbergja #info sandbergja is Jane Sandberg, Linn-Benton Community College
14:02 ohiojoe #info ohiojoe is Joe Knueven, Germantown Public Library, COOL
14:02 jihpringle #info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka)
14:02 dluch joined #evergreen
14:03 dluch joined #evergreen
14:04 ohiojoe anyone else?  :-)
14:04 dluch Sorry, I'm here...having IRC issues
14:05 ohiojoe no worries, please introduce yourself for the sake of the record
14:05 kmlussier #info kmlussier is Kathy Lussier, MassLNC
14:06 ohiojoe next month I'll need to remember to actually use the topic command for introductions...
14:06 dluch #info dluch is Debbie Luchenbill, MOBIUS
14:06 BAM_ #info BAM is Benjamin Murphy, NC Cardinal
14:07 ohiojoe #topic Ongoing Business
14:08 ohiojoe #topic Progress on documentiong new features in Evergreen 2.12 (and previous)
14:09 ohiojoe Does anyone have any updates on this?  My recollection is that action items 6 and 7 came out of our discussion about this last month
14:11 ohiojoe and I can sadly report, that local events during the last several weeks lead to me neglecting to act on my particular action item there..
14:11 jihpringle we haven't had anytime recently to contribute back but all of our docs have been updated to 2.12 if anyone wants/has the time to copy from them
14:11 sandbergja ohiojoe: no worries; I only got around to finishing my piece this morning
14:12 sandbergja jihpringle++
14:12 ohiojoe jihpringle++
14:13 dluch I've pretty much neglected my plans for contributing, too.  Sorry
14:13 kmlussier I haven't been able to devote much time to docs over the past month either.
14:13 dluch jihpringle++
14:14 ohiojoe No worries, well, moving along then
14:14 sandbergja I'm curious -- how did the recent web client day go?
14:15 sandbergja Sorry that I wasn't able to participate; that day turned out to be way busier than I expected. :-(
14:15 kmlussier Sadly, I don't think there was much activity. It was my first day back from vacation, and I didn't send out a reminder until late morning.
14:15 kmlussier It was also the day of the maintenance release, and I ended up focusing on the release instead of docs.
14:15 kmlussier I have no vacations coming up before the next web client day, and I plan to promote it more heavily.
14:16 ohiojoe I had wanted to use it as a nudge to get moving on docs work too, but ended up at an out of town meeting instead..
14:16 kmlussier #info Next web client documentation day is September 27
14:18 ohiojoe #topic Progress on Docs Reorganization Project
14:18 sandbergja kmlussier: Thanks for your promotion work!
14:19 sandbergja We got some pretty positive feedback on the general direction of the docs reorg project!
14:19 kmlussier Yes, it all looked good! sandbergja++
14:19 dluch Yes!  sandbergja++
14:20 ohiojoe Yeah, I saw that on the general list.  I don't think I saw anything that looked like less than positive feedback
14:20 jihpringle sandbergja++
14:20 ohiojoe sandbergja++
14:20 sandbergja I think, at this point, it's time for the "Where do we go from here?" question
14:20 kmlussier I think we should switch it over.
14:20 dluch Agreed
14:20 jihpringle agreed
14:20 ohiojoe sounds good to me
14:21 ohiojoe let's see, there's a command here for this..
14:21 sandbergja Should we plan for 3.0, then?  I think it would be messy, and some things would be in the wrong books.
14:22 sandbergja But it could still provide some usability benefits?
14:22 sandbergja Also, new major release = new presentation of documentation sounds fun!
14:22 kmlussier Yes, I think that makes sense. So the organization for the other releases would remain the same?
14:22 jihpringle I think 3.0 makes the most sense, since most of the docs are having to be touched anyways with new screenshots for the webclient
14:22 dluch Yes!
14:23 ohiojoe yeah, even if there's some messiness, a major release is a good time to introduce such a change in the docs..
14:23 sandbergja kmlussier: I think just doing 3.0 docs sounds safer
14:23 kmlussier +1
14:24 ohiojoe so, are we agreeing to change the structure starting with the 3.0 docs?
14:24 jihpringle +1
14:25 kmlussier I don't think the 3.0 docs are added until the major release day, which is October 3. Maybe we could look at updating master now so that we have time to troubleshoot any issues that arise?
14:25 sandbergja That makes sense.  Switching it over would be a 3-step process:
14:26 sandbergja 1) Getting the new root_*.adoc files into master (these determine which content is in which books)
14:27 sandbergja 2) Updating the script on the production docs server to generate the new, reorganized manuals based on the root_*.adoc files
14:27 sandbergja 3) Lots and lots of cleanup :-)
14:28 kmlussier sandbergja: I assume Robert hast to take care of #2?
14:29 sandbergja kmlussier: I think so.  There's a reorganized-documentation-generator script on the docs testing server that would just need a few modifications.
14:31 kmlussier OK, so I guess we need to coordinate a bit to make sure he can update the script right after the new root file is added.
14:32 sandbergja I believe that the current script would just ignore the new files, so it wouldn't be terrible if there were a lag between 1 and 2.
14:32 sandbergja But doing 2 before 1 would cause problems. :-)
14:32 sandbergja I'm wondering if 1) and 2) should be action items for me?
14:33 ohiojoe that sounds good to me
14:33 kmlussier And 3 should be an action item for the rest of us. :)
14:33 ohiojoe I was thinking it sounds like an action item, and like something that only a few of y'all know what to do/how to do it
14:34 sandbergja Maybe #3 could be coordinated in the wiki?
14:34 ohiojoe #action sandbergja will coordnate getting the new root_*.adoc files into master
14:34 dluch That's a good idea
14:34 sandbergja The cleanup that I mean is stuff like "There is random administrator stuff in the middle of the circ manual; please move it to the admin manual"
14:34 ohiojoe #action sandbergja will coordnate updating the script on the production doc server to generate the new, reorganized manuals based on the root_*.adoc files
14:35 ohiojoe #action everyone will work on cleaning up the reorganized documentation
14:36 kmlussier Should somebody take an action item to get that wiki page started?
14:36 jihpringle I'll start the wiki page
14:36 sandbergja jihpringle: thanks!
14:36 kmlussier jihpringle++ sandbergja++
14:37 ohiojoe #action jihpringle will start a wiki page to coordinate the cleanup on the reorganized docs
14:37 ohiojoe jihpringle++ sandbergja++
14:37 dluch jihpringle++ sandbergja++
14:38 ohiojoe #agree the reorganized documentation structure will be applied starting with the 3.0 documentation
14:38 abneiman #info abneiman = Andrea Neiman, EOLI
14:38 abneiman (apologies, I had another meeting)
14:38 ohiojoe no worries
14:40 ohiojoe #topic progress on documentation launchpad bugs
14:41 ohiojoe #link https://bugs.launchpad.net/evergr​een/+bugs?field.tag=documentation
14:41 ohiojoe does anyone have anything to report here?
14:42 kmlussier nope
14:43 dluch No, sorry
14:43 ohiojoe in that case, moving swiftly along
14:43 ohiojoe #topic old business
14:43 ohiojoe #topic progress on Web Client docs
14:44 kmlussier Yes, I think we covered that above when we talked about the web client documentation days.
14:44 ohiojoe mm, very true
14:45 sandbergja I had a quick question about it
14:45 ohiojoe please
14:45 sandbergja I saw a Cataloging doc staff client rewrite mentioned in the 2.12 doc needs wiki page
14:45 sandbergja Does anybody have details to share about this?
14:46 sandbergja Especially, should others hold off on contributing cataloging-related documentation until this re-write is done?
14:46 sandbergja akilsdonk: is this a project you are working on?
14:46 kmlussier sandbergja: Remind me. What's the link for that page?
14:47 sandbergja #link https://wiki.evergreen-ils.org/doku.php?​id=evergreen-docs:2.12_needs#cataloging
14:48 jihpringle I'm not seeing it on that page, am I completely missing it?
14:48 jihpringle nm, just saw where it is
14:48 kmlussier abneiman: Do you know anything about it?
14:49 abneiman kmlussier: sorry, I don't -- akilsdonk would be the one to ask, but I don't think she's available right now
14:50 * kmlussier hopes it means akilsdonk is doing all the cataloging docs for the web client. :D
14:50 sandbergja abneiman: would you mind checking in with her?
14:51 abneiman sure, but I do not think she is documenting the entirety of webby cataloging :)
14:51 kmlussier Darn!
14:51 ohiojoe shucks
14:51 dluch Bummer
14:51 dluch lol
14:51 sandbergja hahaha hope springs eternal
14:51 ohiojoe shall we make that an action item?
14:52 abneiman sure
14:53 ohiojoe #action abneiman will check on the 2.12 cataloging docs rewrite undertaken by akilsdonk
14:54 ohiojoe #topic previous action items
14:55 sandbergja I'm wondering if we could dispense with the missing RDA content action item?
14:55 kmlussier yes
14:55 kmlussier please
14:55 ohiojoe will do
14:55 ohiojoe excellent
14:55 jihpringle sandbergja: I searched through my email this morning and could not find anything
14:55 sandbergja jihpringle: thanks for checking!
14:55 jihpringle so +1 to dispensing it
14:55 kmlussier I think that action item started with me about two years ago.
14:56 ohiojoe looking at them, with Christineb not here, that leaves just 4 and 5..
14:56 kmlussier nope
14:56 kmlussier I inadvertently took one of Christineb's action item.
14:56 jihpringle I'm sure Christineb has no problem with that kmlussier :)
14:57 kmlussier We now have an Evergreen-specific YouTube channel. I had forgotten it was discussed at the last meeting.
14:57 ohiojoe excellent
14:57 dluch Yay!
14:57 kmlussier But I will take an action item to see if I can get ChristineB linked up to that channel.
14:57 sandbergja kmlussier: I think that your 3.0 video would be a good fit for Christineb's playlist too!
14:58 sandbergja In the spirit of action item #4
14:58 ohiojoe Does that mean that 1 and 2 are complete, or just #2?
14:58 kmlussier #1 hasn't been done. I think we should probably move the videos to the Evergreen channel before adding the link.
14:58 kmlussier Also, please subscribe to the channel. We need 100 subscribers to get a custom URL.
14:59 ohiojoe ok, that makes good sense.  I can leave that in there for now then
14:59 kmlussier #link https://www.youtube.com/chan​nel/UC83L8WyXoj8Kf9hShdDY61A
14:59 jihpringle kmlussier: Christineb is on vacation this week, back next week
14:59 dluch Just subscribed!
15:00 ohiojoe #action everyone should subscribe to the Evergreen-specific YouTube channel
15:00 dluch kmlussier++
15:00 ohiojoe I just did as well..  and with that, any other last minute things before we close the meeting?
15:00 ohiojoe kmlussier++
15:00 abneiman one thing from me
15:01 ohiojoe please
15:01 sandbergja kmlussier++
15:01 abneiman I have a pullrequest up on github for Offline Circulation for the web client; I didn't want to straight up replace the XUL Offline
15:02 abneiman but that's there if someone wants to look at it.  I may have even done it correctly (maybe) :)
15:02 sandbergja abneiman++
15:02 abneiman akilsdonk++ (I had lots of help)
15:02 kmlussier abneiman: We've been replacing XUL documentation for anything in 2.12 or later.
15:03 mmorgan1 joined #evergreen
15:03 ohiojoe abneiman++
15:03 dluch Cool.  abneiman++
15:03 kmlussier abneiman++ akilsdonk++
15:03 ohiojoe and with that..
15:03 ohiojoe #endmeeting
15:03 pinesol_green Meeting ended Thu Sep  7 15:03:25 2017 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:03 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2017/evergreen.2017-09-07-14.01.html
15:03 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2017/evergreen.2017-09-07-14.01.txt
15:03 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2017/evergreen.2017-09-07-14.01.log.html
15:03 ohiojoe thank you everyone
15:03 dluch Thanks, ohiojoe!
15:04 dluch ohiojoe++
15:04 kmlussier ohiojoe++
15:04 jihpringle ohiojoe++
15:04 sandbergja ohiojoe++
15:04 * dluch successfully managed to be at DIG, on a conference call meeting, and eat lunch at the same time
15:04 abneiman ohiojoe++
15:04 abneiman dluch++ # multitasking champ
15:04 ohiojoe that is some serious skills dluch
15:04 ohiojoe dluch++
15:05 sandbergja dluch++
15:05 jihpringle sandbergja kmlussier: we're getting ready to switch from docbook to asciidoc for our local docs and wondering if it's possible to get a copy of CSS style sheets used for the community docs and if so who I should be asking?
15:07 kmlussier jihpringle: Probably Robert Soulliere is the best person to ask.
15:07 jihpringle thanks, I'll email him
15:07 kmlussier jihpringle: Possibly remingtron or yboston?
15:07 sandbergja jihpringle: You can download the CSS at http://docs.evergreen-ils.​org/2.12/evergreen_doc.css
15:08 sandbergja but there's a lot that I don't understand about how asciidoc gets styled, apart from the CSS
15:08 kmlussier sandbergja++
15:08 jihpringle great, I'll give that to our sys admin and see if that's what he needs
15:09 jihpringle thanks :)
15:10 sandbergja no problem!
15:10 sandbergja good luck with the docbook/asciidoc switch!
15:12 jihpringle thanks!  we figured we were going to have to update everything for the web client anyways, so the right time to make the switch
15:12 jihpringle hopefully it will make it easier for us to contribue back to the community docs
15:15 jihpringle ohiojoe: here's the link for the re-org clean up wiki page if you want to include in the agenda for next month - https://wiki.evergreen-ils.org/doku.​php?id=evergreen-docs:reorg:clean_up
15:16 ohiojoe excellent.  Thank you
15:16 jihpringle np
15:17 sandbergja jihpringle++
15:17 ohiojoe jihpringle++
15:18 jihpringle sandbergja++ the CSS link is what we needed!
15:20 dbs jihpringle++ # let me know if you need the command I used to convert docbook -> asciidoc during the conference
15:21 jihpringle thanks dbs++
15:26 _bott_ Documenting for posterity... I just chased my tail for a bit trying to figure out why my Web client would only return a Forbidden. I had enabled Indexes for /openils/var/web, and that seems to have been the issue. By adding/removing that Option I can easily recreate/correct the problem.
16:00 mmorgan joined #evergreen
16:14 jeffdavis kmlussier: did MassLNC ever get anywhere with new feature dev on allowing other patrons to pick up a patron's holds?
16:15 kmlussier jeffdavis: bug 1661688
16:15 pinesol_green Launchpad bug 1661688 in Evergreen "Want easy way to clear a hold when picked up by other patron" [Wishlist,New] https://launchpad.net/bugs/1661688 - Assigned to Dan Pearl (dpearl)
16:15 kmlussier C/W MARS is working on it, but there was an issue when I tested it.
16:46 Jillianne joined #evergreen
17:02 pinesol_green News from qatests: Test Success <http://testing.evergreen-ils.org/~live>
17:05 mmorgan left #evergreen
17:10 jvwoolf left #evergreen
17:30 dbwells joined #evergreen
17:55 gmcharlt webby is now back up and running the beta
20:38 rkw joined #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat