Evergreen ILS Website

IRC log for #evergreen, 2015-04-02

| 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
04:08 sarabee joined #evergreen
05:57 gsams joined #evergreen
07:53 mrpeters joined #evergreen
08:00 Newziky joined #evergreen
08:10 collum joined #evergreen
08:11 rjackson_isl joined #evergreen
08:34 mmorgan joined #evergreen
08:45 ericar joined #evergreen
08:46 graced joined #evergreen
08:50 kmlussier @coffee
08:50 * pinesol_green brews and pours a cup of Kenya AA Nyeri Fine Cup, and sends it sliding down the bar to kmlussier
08:51 kmlussier good morning #evergreen
08:55 mmorgan Good Morning!
08:55 kmlussier @tea [someone]
08:55 * pinesol_green brews and pours a pot of BH02: Holy Basil Purple Leaf, and sends it sliding down the bar to remingtron (http://ratetea.com/tea/upton/bh0​2-holy-basil-purple-leaf/1937/)
08:55 * kmlussier wonders why pinesol_green serves coffee and tea at a bar.
08:56 jboyer-isl Classy bar or tea dive?
08:56 jwoodard joined #evergreen
08:59 Newziky1 joined #evergreen
09:00 Dyrcona joined #evergreen
09:00 remingtron jboyer-isl: would I be found in a tea dive? I think not! Well, maybe.
09:01 jboyer-isl I would actually very much like to see such a thing as a tea dive, though perhaps only once.
09:02 remingtron kmlussier: thanks for the tea, I always drink Holy teas near Easter.
09:04 kmlussier I picture a darkened room, a person with his/her head lying on the bar, begging for just one more cup of Earl Grey.
09:05 jeff huh. i guessed that tea would be one from Upton Tea Imports (aside from the url having "upton" in it, which was a pretty big clue).
09:06 jeff (the prefix/code before the name was what gave it away)
09:06 jeff http://ratetea.com/search/?only=tea&brand_id=1
09:07 kmlussier Tea made with basil doesn't sound appealing to me.
09:08 dbwells Review from that site for this tea, "it reminds me of the smell of books".  It was stated as a good thing :)
09:10 Dyrcona @blame ejabberd
09:10 pinesol_green Dyrcona: Your failure is now complete, ejabberd.
09:21 jlundgren joined #evergreen
09:36 jboyer-isl kmlussier, re: 09:04:43, "Gimmie the one with bergi, bergimi, berger... bergamot. Double."
09:38 kmlussier jboyer-isl: Ha ha. I suspect you weren't being totally honest when you said you hadn't been to a tea dive before.
09:39 akilsdonk joined #evergreen
09:41 maryj joined #evergreen
09:41 jboyer-isl No tea dives yet, just dive dives. They're usually... not my cup of tea.
09:41 Dyrcona I'll have a scotch on the rocks. My friend takes his neat.
09:44 bshum :D
09:44 Dyrcona Heh. Thought you'd get it. :)
09:45 csharp now we need to find a tea dive in Hood River
09:46 csharp for us teetotalers to get our drink on
09:46 csharp teatotalers!
09:46 Dyrcona You mean teatotalers?
09:46 csharp jynx!
09:47 collum https://www.facebook.com/thegoodmedicinelounge
09:47 * csharp quickly trademarks the name and makes millions
09:47 Dyrcona I don't drink Earl Grey any more for....digestive reasons. Begamot apparently doesn't agree with me.
09:47 csharp collum++
09:47 * csharp likes Earl Grey, Hot
09:51 kmlussier collum++
09:52 kmlussier I would be up for a trip to the tea room.
09:52 collum ditto
10:13 darshana joined #evergreen
10:16 yboston joined #evergreen
10:28 mllewellyn joined #evergreen
10:31 Shae joined #evergreen
11:00 eeevil csharp: so, I was thinking  about your "all books" filter, and it looks like you're not using the new, stock composite record attr def for "books".  in your example, QP is seeing item_type(a,t) but should be seeing search_format(book) ... so, either I'm misunderstanding the question or there's something configuration-based going on
11:03 TaraC joined #evergreen
11:04 csharp eeevil: is there a table I can dump out and share with you to verify?
11:06 eeevil not just one. it's ... complicated in the back end :)  ... are you familiar with http://docs.evergreen-ils.org/2​.6/_marc_record_attributes.html ?
11:07 eeevil the UI looks like it wants to use the right thing, but it's getting mapped away somehow, maybe. local customization? but ... I have to run for a while
11:10 csharp eeevil: thanks for the hint - yes Elaine and I did some customization that may be getting in the way - I'll review it and get back to you
11:22 csharp eeevil: I'll add a 'book' example query to the ticket too
11:22 csharp s/ticket/bug report/
11:27 csharp okay - added comment & attachment to bug 1438136
11:27 pinesol_green Launchpad bug 1438136 in Evergreen "OPAC searching significantly slowed by adding format filters" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1438136
11:37 sandbergja joined #evergreen
11:49 kmlussier I need to fill out the acknowledgements info on the Release Notes - http://evergreen-ils.org/documentat​ion/release/RELEASE_NOTES_2_8.html.
11:49 kmlussier I need help for the second on organizations that commissioned development.
11:49 kmlussier I know MassLNC and C/W MARS commissioned development projects that made it into 2.8.
11:50 kmlussier If anyone else worked on a contracted development project that made it into 2.8, could you let me know who should receive the credit for commissioning the development?
11:52 bshum Hmm
11:53 kmlussier Oh, and Georgia PINES should be there too.
11:54 ningalls joined #evergreen
12:06 jihpringle joined #evergreen
12:09 berick kmlussier: KCLS (via me) did the 2.3.1. Vandelay Authority Record Match Sets
12:11 kmlussier berick: Thanks. I'll inlcude KCLS in the section for organizations whose employees contributed patches.
12:12 kmlussier I've got most of those orgs nailed down because it's easy to find the dev who did the work. Not so easy to find project funders.
12:12 berick ah, gotcha
12:12 berick thanks
12:12 * kmlussier doesn't think there was much commissioned development for 2.8
12:16 bmills joined #evergreen
12:26 berick hmm, need to bump all the 2.8.0 LP tix
12:27 berick i forget, is there an auotmated way to do that?
12:27 bshum Not really.
12:27 bshum Though there is an LP account used for changing statuses, etc.
12:27 graced NC kmlussier: Cardinal had commissioned work
12:27 kmlussier graced: Thanks!
12:28 graced do you need LP links?
12:28 bshum berick: I can help you take care of it, if it'd be helpful.
12:29 kmlussier graced: I don't need them for the release notes, but I'm always curious about what work was commissioned by different groups. :)
12:29 graced https://bugs.launchpad.net/evergreen/+bug/1378169
12:29 graced and
12:29 graced https://bugs.launchpad.net/evergreen/+bug/1287370
12:29 pinesol_green Launchpad bug 1378169 in Evergreen "The context OU selector in funds management should be sticky" (affected: 2, heat: 12) [Wishlist,Fix committed]
12:29 pinesol_green Launchpad bug 1287370 in Evergreen "Funds Go Back Option Takes User Back to the First Fund Screen" (affected: 5, heat: 26) [Low,Fix committed]
12:29 kmlussier Just because I'm nosy
12:30 berick bshum: looks like there's only 3 open tickets for 2.8.0.  i'll just move them.
12:30 berick thanks, though
12:30 bshum Sounds good.
12:31 * kmlussier now realizes there is also a new feature missing from the release notes.
12:31 kmlussier Of course, it was one I signed off on, so I should have caught nearly 2 months ago.
12:33 bshum berick: I'm moving a few of the bugs left at 2.8-beta that didn't get worked on to either 2.next or 2.8.1 (if they're looking like bugfixes)
12:34 csharp general philosophical question to the channel: should we start considering C compiler warnings as individual bug reports?  discuss
12:35 bshum csharp: I'm going to respond with "eh?" and wonder what warnings you mean :
12:35 bshum :)
12:35 csharp having just spent the better part of two hours trying to get dpkg-buildpackage to not treat format-security warnings as fatal errors, that question is on my mind ;-)
12:36 berick thanks, bshum
12:36 csharp example (that I'm pasting in channel, yes)
12:36 csharp utils.c:133:2: error: format not a string literal and no format arguments [-Werror=format-security] return snprintf( *(global_argv), global_argv_size, VA_BUF ); ^
12:36 csharp ah - that came out as one line here ;-)
12:37 csharp that particular warning is from building OpenSRF on Ubuntu 14.04
12:37 csharp gcc 4.8.2
12:39 csharp for the logs/the curious, I was able to circumvent the fatality of those errors by adding 'export DEB_CFLAGS_MAINT_APPEND= -Wno-error=format-security' to my debian rules file
12:39 csharp but the real solution would be to fix the causes of the warnings
12:44 bshum berick: Since I'm in there, I'm also updating statuses from fix committed to fix released using the bugmaster account now.
12:45 berick bshum++
12:48 bshum csharp: In general, I think if you've got some suggestions on how to address some of those warnings/errors you're seeing, it doesn't hurt to add them as LP tickets and target them towards the next OpenSRF milestones for review.
12:48 bshum Or at the very least, noting them for further scrutiny by smarter folks than I :)
12:53 kmlussier berick/dbwells: While I'm in the Release Notes, do we need to say anything there about the changes to the fine generator?
12:53 csharp yeah, I think I'll start a couple o' tickets on 'em
12:53 * csharp has a feeling they'll be more urgent when jessie is released
12:53 bshum Which is soon I hear.
12:54 bshum April 25 - https://lists.debian.org/debian-de​vel-announce/2015/03/msg00016.html
12:54 dbwells kmlussier: I don't think so.  There should be no change in functionality.
12:54 berick kmlussier: well, ideally, no one would ever know it changed.
12:54 berick jinx
12:55 csharp big changes in installation instructions for jessie - new-style ejabberd config, for one
12:56 * csharp started a branch with README changes, originally based on Fedora 21, but ejabberd is utterly broken out of the box on Fedora http://git.evergreen-ils.org/?p=working/OpenSRF.gi​t;a=blobdiff;f=README;h=cc81d4492bd9f1aed2cded2366​6254b7fa12cfbe;hp=38aff45713816207e2607afe4b1dfdb8​efdf7f52;hb=e5ff2480d51feffee388e52104c2c592d37205​d3;hpb=2cf93448e2ba2540b7fc3ea2f939f62621488420
12:56 pinesol_green [opensrf|Bill Erickson] LP#1418613 per-tab websocket send() JS thinko repair - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=2cf9344>
12:57 kmlussier dbwells / berick: OK, thanks
12:58 bshum csharp: Did you say Fedora, but mean Jessie?  Or do you mean Jessie also has newer ejabberd packaged with it, like Fedora's?
12:58 * bshum knows that initial makefile stuff was pushed for Jessie, but hasn't watched it closely since he doesn't use Debian.
12:59 csharp bshum: jessie also has the newer YML-based config, like Fedora
12:59 csharp but jessie's ejabberd appeared to work fine in my scant testing
12:59 csharp s/YML/YAML/
13:05 bshum Okay, done bug wrangling for now.
13:06 ericar joined #evergreen
13:13 b_bonner joined #evergreen
13:14 rashma joined #evergreen
13:15 kmlussier I'm confused. I see a commit for the creation of RELEASE_NOTES_2_8.txt, but I don't see the actual file.
13:16 kmlussier Oh, I see. It's in the 2_8 branch, but not in master.
13:16 csharp @praise [someone]
13:16 * pinesol_green jboyer-isl is kind and patient to newbies
13:17 csharp @dessert [someone]
13:17 * pinesol_green grabs some wild Alaskan rhubarb pie for yboston
13:17 jboyer-isl Until the velvet glove of patience is removed, then it's iron fist, noob.
13:17 csharp jboyer-isl: haha
13:19 * csharp is reminded of the "Stonecutters" Simpsons episode: "Remove the Stone of Shame!  Attach the Stone of Triumph!"
13:20 * jboyer-isl needs to watch more Simpsons. Long has been the drought.
13:21 kmlussier berick: Should bab547295d1fd77b7db09108af02ac563f4ab1df go into master too?
13:21 pinesol_green [evergreen|Bill Erickson] 2.8 release notes creation and cleanup - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=bab5472>
13:21 csharp jboyer-isl: my Simpsons devotion ended nearly 20 years ago, but I own the seasons love and watch them very often
13:21 csharp s/seasons love/seasons *I* love/
13:22 csharp they got a bit unmoored in the mid- to late 90s and I never really watched them after that
13:24 berick kmlussier: hmm, yes.  thanks.  will merge...
13:24 kmlussier berick++ #Thanks!
13:25 buzzy joined #evergreen
13:40 eeevil csharp: re your compiler warning, that's how we rewrite the process title for top/ps ... we could look for other ways to do it, maybe, but it's "considered safe" in the context we use it (we control the strings -- it would take a malicious installation to exploit)
13:41 eeevil in which case, you have bigger issues ;)
13:46 csharp eeevil: makes sense
13:47 csharp the CFLAGS for debian package building add -Werror=format-security, so that's why it was breaking when trying to build a deb
13:53 jboyer-isl Sounds like a good use for #pragma diagnostic push / ignore=format-security / pop : https://gcc.gnu.org/onlinedocs/gcc/Diag​nostic-Pragmas.html#Diagnostic-Pragmas (on GCC at least... do any other supported OSs use Clang or PCC?)
13:53 kmlussier Heh, we're still getting paxed in our Release Notes acknowledgements. :)
13:53 csharp paxed++
13:53 bshum paxed++
13:54 jeff goes to show, bugs you report can have lasting impact! :-)
13:56 paxed hah
13:57 rsoulliere joined #evergreen
13:57 yboston heads up, the DIG monthly meeting will be starting at 2 PM EST
13:58 paxed oh, and just as a note: for GCC, "all" in -Wall does not actually mean all...
14:00 yboston #startmeeting DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting.
14:00 pinesol_green Meeting started Thu Apr  2 14:00:31 2015 US/Eastern.  The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00 pinesol_green The meeting name has been set to 'dig_monthly_meeting_evergreen_documentati​on_interest_group__dig__monthly_meeting_'
14:00 yboston The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?i​d=evergreen-docs:dig_meeting_20150402-agenda
14:00 yboston #topic Introductions
14:00 yboston Please feel free to start introducing yourselves...
14:01 yboston #info yboston is Yamil Suarez @ Berklee College of Music - DIG meeting facilitator
14:01 rsoulliere #info rsoulliere is Robert Soulliere, Mohawk College
14:02 jihpringle info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka)
14:02 kmlussier #info kmlussier is Kathy Lussier, MassLNC
14:02 jihpringle #info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka)
14:03 yboston welcome everyone
14:04 yboston Robert or Kathy, do either of you have anything to report?
14:04 yboston it is OK if you don't
14:04 kmlussier I do
14:04 yboston go ahea
14:04 yboston *ahead
14:04 kmlussier #topic Release Coordinator Report
14:04 kmlussier #info I am adding acknowledgements plus one missing feature to the Release Notes as we meet
14:05 kmlussier #info The 2.8 Release Notes should be complete by the end of today.
14:05 kmlussier End of report
14:05 kmlussier Oh, I do have something else.
14:05 yboston BTW, Kathy do you have any doceumntation ont he process of making the release ntoes?
14:06 kmlussier There has been some talk among the devs of possibly doing release notes for point releases. That's something I might like to consider doing if I have time for the 2.8 point releases.
14:06 pinesol_green [evergreen|Bill Erickson] 2.8 release notes creation and cleanup - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=eee6a71>
14:06 kmlussier yboston: No, I don't have documentation. Is this documentation for devs who are writing release note entries?
14:06 kmlussier Ha, nice timing berick
14:06 yboston no, for the documentation side
14:06 yboston in case you ever need a sub
14:07 yboston or help
14:07 kmlussier No, I don't have documentation because, as long as the devs do their release notes, I don't do much other than read them for clarity and add acknowledgements.
14:07 kmlussier I do go through the ChangeLog to make sure everything is there.
14:07 yboston OK
14:07 kmlussier I can add something to the wiki, though.
14:07 yboston I thought it was more involved
14:08 yboston if you have the time, even a high level overview could be helpful
14:08 kmlussier No, I think what the RM does is a little more involved.
14:08 yboston yes, I agree
14:08 kmlussier In terms of generating the Release Notes, that is.
14:08 yboston Robert did you want to mention anything?
14:08 rsoulliere I have a couple of items.
14:09 yboston go ahead
14:09 rsoulliere #topic Conversion Coordinator Report
14:09 rsoulliere #info Evergree Documentation for 2.8 is up and pulling for the rel_2_8 branch.
14:09 rsoulliere #link http://docs.evergreen-ils.org/2.8/
14:09 kmlussier rsoulliere++
14:09 rsoulliere #info I have updated the 2_8 repository to include the 2.8 release notes.
14:09 yboston rsoulliere++
14:09 rsoulliere #info I have also added the 2.8 database schema documentation.
14:10 rsoulliere #info Links have been added to the documentaiton menu page:
14:10 rsoulliere #link http://docs.evergreen-ils.org/
14:10 rsoulliere #questions any updates on the new doc servers?
14:11 yboston I think the web group met yesterday
14:11 yboston and they mentioned that they have an IP address and that thet need to still create the VM
14:12 yboston kmlussier: where you at the meeting yesterday?
14:12 kmlussier yes
14:12 yboston am I remembering correctly that you know of?
14:12 kmlussier Yes, that's what gmcharlt reported
14:13 yboston kmlussier: thanks
14:13 yboston I can follow up for next time to see what the progress is
14:13 yboston #action yboston will check in on DIG VM
14:13 rsoulliere OK, sounds good. That is all I had for today.
14:14 yboston thanks
14:14 yboston I will move on to past meetign action items
14:14 yboston #topic past meeting action items
14:14 yboston #info 1 ) yboston will reach out to krvmga for another copy of his docs to push to master
14:15 yboston I did not get a chance to do this, will defer for next time
14:15 yboston #info 2 ) kmlussier will complete the marc stream importer work and check on the status of the RDA docs
14:15 yboston kmlussier: any updates ont his?
14:15 kmlussier I need to defer for next time. My plan is to create my own DIG day to work on my to-do list
14:16 yboston OK
14:16 yboston #action kmlussier will complete the marc stream importer work and check on the status of the RDA docs
14:17 yboston the next two items were assigned to remingtron; but I am not sure if he is here?
14:17 yboston will defer them for now
14:17 yboston #action remingtron will send out email to list about cahnging the file suffix in the docs repo to .asciidoc
14:17 yboston #action remingtron will send an email to the list to consider changing the AsciiDoc section header style
14:18 yboston the next item was for the whole group
14:18 yboston #info 5 ) all decide how to proceed with docs reorganization next meeting
14:18 jck_ joined #evergreen
14:18 yboston this might be a good topic of discussion at the conference
14:18 remingtron #info remingtron is Remington Steed, Hekman Library (Calvin College)
14:18 remingtron (sorry so late)
14:19 yboston hola
14:19 remingtron may I give a quick update on my two action items?
14:19 yboston not sure  if you have read what we have gone over so far
14:19 yboston go right ahead
14:21 remingtron I have not initiated either of those conversations yet. I still plan to do the first, but not the second (header style syntax) since consensus was to allow individual choice, and I have come to agree
14:21 yboston makes sense
14:21 remingtron that's all I wanted to say :)
14:22 yboston not sure how to cancel one for the defered actions with meetbot, but I on't think it is a big deal
14:22 yboston thank remingtron
14:23 yboston so right before remingtron joined us I had just brought up the topic of "5 ) all decide how to proceed with docs reorganization next meeting"
14:23 yboston I had also mentioned this might be a good topic for the upcoming conference
14:23 yboston any comments or questiosn about the re-org goal?
14:24 kmlussier #info remingtron will NOT send email to the list to consider changing AsciiDoc section header because the consensus was to allow individual choice.
14:24 kmlussier For the minutes. :)
14:24 remingtron kmlussier++
14:25 yboston we can also defer the topic of the re-org for next meeting, if that is what we want to do as group today
14:25 remingtron I created a wiki page with some re-org ideas here:
14:25 remingtron #link http://evergreen-ils.org/dokuwiki/doku.php?id=ev​ergreen-docs:reorg_2014:audience_focused_layout
14:26 kmlussier It seems like the in-person meeting is a great opportunity to discuss something like a doc reorg.
14:26 remingtron I'd be glad for any input or reactions
14:26 Newziky1 left #evergreen
14:26 remingtron and FYI, I'm not able to attend the conference this year
14:26 yboston we need to plan to have a laptop to stream the meeting for those that cannot make it
14:27 remingtron so I'll do my best to participate remotely
14:27 remingtron yboston: thanks!
14:27 yboston or a phone on speaker phone
14:27 yboston (de nada)
14:27 yboston remingtron: that links looks pretty good
14:28 yboston *link
14:28 remingtron all are welcome to edit and expand that wiki page
14:29 yboston should we stay ont his topic or move on?
14:29 yboston the other two major topics arae web clients and EG 2.8 new feature docs
14:30 remingtron I'm happy to move on
14:30 yboston good enough for me
14:31 yboston #topic Progress on documenting new features in Evergreen 2.8
14:31 yboston #link http://evergreen-ils.org/dokuwiki/d​oku.php?id=evergreen-docs:2.8_needs
14:32 kmlussier I got about half-way through my assigned topics.
14:32 yboston we still have a few features that need documenting.
14:32 yboston I just realized I signed up for a second feature I need to document
14:32 kmlussier I decided to do a new section regarding all billing OU settings, so it became a bigger project than I originally intended.
14:32 yboston I see
14:33 yboston that is what happens when adding new features :)
14:33 kmlussier I also could document most of the items in the OPAC section, but I didn't want to sign up until I had finished my first two items. :)
14:33 yboston some of those OPAC ones could be really simple, and great for a beguiner
14:33 kmlussier Two of them are mine, so I feel a responsibility to document them.
14:34 kmlussier yboston: Yes, I agree. I was thinking they would be good for a beginner too.
14:34 kmlussier In some cases, it may just require checking to see if a screenshot needs to be replaced.
14:35 yboston worse case scenario, we can use this low hanging fruit to give to newcomers at the conference. Though I am sure we would rather be done with 2.8 beofre the conference
14:36 yboston also, thanks to I think remingtron for sending out reminders aout 2.8 new features ont he list
14:37 yboston #action all finish outstanding EG 2.8 features listed here http://evergreen-ils.org/dokuwiki/d​oku.php?id=evergreen-docs:2.8_needs
14:38 yboston should we switch to talking about web client docs?
14:39 remingtron I have one comment
14:39 remingtron (sorry, not paying close enough attention today!)
14:39 yboston go ahead
14:40 remingtron I realized that any time we don't document a feature on a given version, it's hard to remember to go back and work on those.
14:40 rjackson_isl :q
14:41 yboston remingtron: I agree
14:41 remingtron I'd like to add a section at the bottom of the 2.8 docs needs wiki page called "From older versions" or such, which lists all outstanding docs features needing new docs
14:41 remingtron thoughts?
14:42 yboston I think it would be helpful
14:43 kmlussier sure, why not?
14:43 yboston though some of it would have to be moved over when we do the 2.9 page, though I don't think that is a problem
14:43 remingtron okay, I'll work on that for 2.8 at least
14:44 yboston should I make it an action item?
14:44 remingtron then DIG can use that list at the conference for any outstanding items
14:44 remingtron yboston: sure!
14:44 yboston good idea
14:45 yboston #action remingtron will add information of older outstanding doc needs to the 2.8 new feature doceumentation wiki page
14:46 yboston any more questions/comments on EG 2.8 docs?
14:47 yboston should we talk about the web client docs?
14:47 remingtron sure, onward
14:47 yboston thanks again to remingtron for sending out an email to remind folks to help reivew some web cleint ocs that were submitted
14:47 yboston we should make that an "all" action item
14:47 yboston for next meeting
14:48 kmlussier Yes, I was just thinking of those. You can give that action item to me if you want.
14:48 kmlussier And I promise I will follow through on that one. :)
14:48 remingtron yboston: I'd put a higher priority on 2.8 docs, and suggest we wait on web client docs
14:49 yboston remingtron: that makes sense;
14:49 yboston we will have plenty of web client docs to work on at the conference
14:49 remingtron but if kmlussier wants an action item, I will not stand in her way!
14:50 kmlussier I just want to review the ones we have.
14:50 yboston #action kmlussier will review submitted web client docs to be included in repository
14:51 yboston any other comments or questions on the topic of web client docs or anything else?
14:52 remingtron just the comment I added to the agenda
14:52 remingtron that we no longer need to wait before backporting web client docs to live docs versions
14:52 remingtron since ESI folks have published their remaining bugs on launchpad
14:52 kmlussier We're backporting to 2.8 then?
14:53 remingtron yes, for as much is included in 2.8, and then 2.9 as more comes outs, etc.
14:54 remingtron though some have already been backported to 2.8
14:55 yboston we are talking about doc commits?
14:56 remingtron yes
14:56 yboston but are we keeping the seperate web client docs sections?
14:56 remingtron yes, still a "preview" version of the docs until the web client is more official
14:56 yboston just makign sure
14:56 remingtron yboston: good clarification
14:57 yboston thank you
14:57 yboston we are almost at the hour mark
14:57 yboston any other commetns or questions before we wrap up?
14:57 remingtron not from me
14:58 yboston OK then, then I will wrap up
14:58 yboston thank you everyone for attending
14:58 yboston #endmeeting
14:58 pinesol_green Meeting ended Thu Apr  2 14:58:57 2015 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
14:58 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2015/evergreen.2015-04-02-14.00.html
14:58 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2015/evergreen.2015-04-02-14.00.txt
14:58 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2015/evergreen.2015-04-02-14.00.log.html
14:59 rsoulliere yboston++
14:59 remingtron yboston++
14:59 kmlussier yboston++
15:28 bmills joined #evergreen
15:29 akilsdonk joined #evergreen
15:40 bmills joined #evergreen
15:47 Callender_ joined #evergreen
16:09 kmlussier My favorite part of the Release Notes is adding the acknowledgements. Because that's where you see in one snapshop all of the different people and organizations that go into making a release happen.
16:17 mmorgan kmlussier++
16:30 chatley joined #evergreen
16:58 kmlussier Hmmm..I can push to the working repository, but when I try to make a doc commit directly to master, I get a message saying I cannot read from the remote repository.
16:58 yboston kmlussier++
16:59 jeff kmlussier: if you type "git remote -v" does your (push) url for the remote in question look like git@git.evergreen-ils.org:/Evergreen ?
16:59 kmlussier Nope
17:00 kmlussier git://git.evergreen-ils.org/Evergreen.git
17:00 kmlussier Is it possible this is my first doc commit since moving to my new laptop in December? I've been negligent.
17:00 kmlussier OK, let me try to figure this out on my own then. I think I can do it.
17:00 kmlussier I WILL master git, even if it kills me.
17:01 jeff if your remote is called "origin", and assuming things are proper on the server side of things already, you can try this: git remote set-url --push origin git@git.evergreen-ils.org:/Evergreen
17:02 kmlussier jeff++
17:02 jeff worked? :-)
17:02 kmlussier It sure did
17:04 kmlussier Isn't there a quote in the database related to git killing people?
17:05 pinesol_green [evergreen|Kathy Lussier] Release Note Acknowledgements - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=0c7df68>
17:05 jeff kmlussier: at least two
17:05 jeff @quote get 1
17:05 pinesol_green jeff: Quote #1: "<senator> much as a cancer would develop from chewing on uranium rocks ... but the tooth decay is lovely!" (added by gmcharlt at 11:22 AM, February 17, 2011)
17:05 jeff @quote get 24
17:05 pinesol_green jeff: Quote #24: "<denials> when git doesn't kill you, it makes you smarter" (added by gmcharlt at 03:58 PM, May 03, 2012)
17:06 * gmcharlt is a little concerned that jeff just happens to have to numbers handy
17:07 jeff gmcharlt: i did my searches via privmsg to avoid cluttering up the channel :-)
17:08 gmcharlt *whew*
17:08 * mmorgan thought jeff must have had them all somewhere in jasperreports ;-)
17:08 * kmlussier thinks jeff really did know them off the top of his head, but doesn't want to admit it. :)
17:09 jeff the missing context from quote 1 is: <senator> my own understanding of the rebase question, the significance of fast-forwards and the consequences of squashing was stunted until it arose organically through habitual git use
17:09 kmlussier jeff: Thank you for that. I was just looking for it, but I couldn't remember how to get to the old logs.
17:10 jeff http://evergreen-ils.org/irc_logs/evergr​een/2011-02/%23evergreen.17-Thu-2011.log
17:11 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:11 kmlussier @quote get 2
17:11 pinesol_green kmlussier: Quote #2: "<tsbere> We need more quotes" (added by berick at 11:24 AM, February 17, 2011)
17:13 berick knowing is half the battle
17:13 berick the easy half
17:18 mmorgan left #evergreen
17:20 akilsdonk joined #evergreen
17:22 gmcharlt kmlussier++ # TODO's contributions will have to wait another year... ;)
17:28 kmlussier That's okay. TODO's contributions were completely overrated anyway.
17:35 chatley_ joined #evergreen
17:36 kmlussier_ joined #evergreen
17:38 mtate joined #evergreen
17:39 bshum joined #evergreen
17:39 mceraso joined #evergreen
19:38 * kmlussier must have had a momentary lapse of memory and thought that berick still worked for ESI
19:41 pinesol_green [evergreen|Kathy Lussier] Release Notes acknowledgements addition - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=984dfe9>
19:48 * eeevil taps desk waiting for pg repo to clone ...
20:58 chatley joined #evergreen

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