Evergreen ILS Website

IRC log for #evergreen, 2014-09-08

| 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
05:03 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
06:02 wsmoak joined #evergreen
07:29 Callender_ joined #evergreen
07:40 mtate joined #evergreen
07:41 eeevil joined #evergreen
07:41 Callender joined #evergreen
07:41 phasefx joined #evergreen
07:42 gdunbar joined #evergreen
07:48 jboyer-isl joined #evergreen
08:02 rjackson-isl joined #evergreen
08:05 mrpeters joined #evergreen
08:05 collum joined #evergreen
08:06 ericar joined #evergreen
08:21 akilsdonk joined #evergreen
08:46 mmorgan joined #evergreen
08:51 dbs @later tell Stompro "git log --follow <path>" is your friend (to follow renames and path changes)
08:51 pinesol_green dbs: The operation succeeded.
08:52 mmorgan left #evergreen
09:01 mmorgan joined #evergreen
09:04 tspindler joined #evergreen
09:21 Dyrcona joined #evergreen
09:23 mtcarlsoz joined #evergreen
09:31 yboston joined #evergreen
09:33 RoganH joined #evergreen
09:35 csharp dbs++ # I didn't know that
09:35 kmlussier joined #evergreen
09:44 Dyrcona joined #evergreen
09:48 pastebot "csharp" at 64.57.241.14 pasted "explain on long running authority heading lookup - why is it not using the by_heading index?" (15 lines) at http://paste.evergreen-ils.org/23
09:48 csharp and... now I have to run to the dentist
09:49 * mrpeters jealous!
09:49 mrpeters not
09:50 mllewellyn joined #evergreen
09:58 sarabee joined #evergreen
10:25 BigRig joined #evergreen
10:57 sudshekhar02 joined #evergreen
11:01 snigdha26 joined #evergreen
11:02 jeff hrm. there's no real way to search a vandelay queue, is there.
11:16 snigdha26 Hello, I am Snigdha, from India. I have written technical blogs as a freelancer and would like to start contributing to open source projects as part of the documentation team. I have already gone through several links about this project, but just thought I would drop in to say hi. Are there any specific guidelines I should keep in mind while starting?
11:18 phasefx snigdha26: welcome!
11:19 snigdha26 phasefx: Hi!
11:20 snigdha26 any pointers for a newbie?
11:20 phasefx snigdha26: I don't write documentation, but if you hang out the channel some of the "DIGgers" may chime in.  But in my mnd, for guidelines... don't let perfection be the enemy of good enough?  small iterations can be better than large chunks
11:22 snigdha26 phasefx: haha, sure! Is there any particular time when they check the IRC?
11:22 mnsri left #evergreen
11:22 phasefx no; I haven't been very active in this channel lately;  You'll want to look for names like yboston and remingtron
11:23 snigdha26 okay! Thanks a lot :)
11:23 phasefx or just say hi on the documentation mailing list
11:24 phasefx better for asynchronicity, but a lot of folks just lurk in channel here and peek in when they're able
11:24 yboston snigdha26: welcome, I work a lot with the offical Evergreen docs. I can help explian things for you
11:24 * phasefx suspected invoking yboston's name would get his attention ;)
11:26 mnsri joined #evergreen
11:27 csharp would someone with postgres/SQL chops be willing to look at my paste from earlier? http://paste.evergreen-ils.org/23
11:27 snigdha26 yboston: Hi! I've already gone through the links given on the website, about the documentation. Are there any ready issues I can start working on? Also I would like to take part in the OPW program if possible. Any specialy guidelines I need to keep in mind for the same
11:29 yboston snigdha26: we do have a couple of lists of things we need help with, some require having access to a copy of Evergreen client software
11:35 snigdha26 yboston: Should I install it right away? Im working on windows right now, but can switch to ubuntu if needed?
11:35 kmlussier snigdha26: Depending on what you are documenting, you could use one of the community demos.
11:35 yboston snigdha26: sorry, I had to take a phone call
11:36 kmlussier snigdha26: http://evergreen-ils.org/dokuwiki/doku.php?​id=community_servers#community_demo_servers
11:36 yboston snigdha26: let me first exlain that overall Evergreen has to sotware parts, the server part, and the client part
11:37 yboston the client can be installed on windows very easily, and you can then connect your client to a community (test) server like Kathy mentioned
11:38 yboston snigdha26: the server part of Evergreen has a lot more steps for installation and cannot be installed on windows.
11:38 yboston usually to write docuemntation for this prject you only need the client
11:39 snigdha26 kmlussier: I'll start with installing the client server then.
11:40 snigdha26 yboston: What part of the documentation can I start working with after that?
11:48 kmlussier snigdha26: We have some small doc needs at http://bit.ly/YqlB8y that might be good to start on.
11:51 ericar_ joined #evergreen
11:52 snigdha26 kmlussier: okay, thanks a lot :) Will get back to you after I look through this
11:55 yboston snigdha26: my apologies again, I had someone else call me.
11:55 yboston snigdha26: I want to make it claer that the Evergreen "server" and the Evergreen "client" are two seprate peices fo software
11:56 yboston snigdha26: The Evergreen cleint is easy to install on Windows. Once you install it you need to point your Evergreen client to one of the Commmunity servers that are already isntalled and running for anyone to use
12:02 snigdha26 yboston: I've installed the Evergreen client
12:06 yboston snigdha26: now you need to conenct your Evergreen client to one of the community servers that kmlussier mentioned earlier here http://evergreen-ils.org/dokuwiki/doku.php?​id=community_servers#community_demo_servers
12:07 yboston snigdha26: when you run the Evergreen cleint, you will see a window that asks for information to connect to an Evergreen server
12:08 yboston like "hostname" , where you would use the URL of one of the test servers listed in the community server link
12:09 yboston though you should not use the "http://" part of the community server. So for the "hotname" value use "demo.evergreencatalog.com" instead of "http://demo.evergreencatalog.com/"
12:11 snigdha26 yboston: I am encountering a network or server failure when I try to enter the workstation name, after logging in
12:11 jihpringle joined #evergreen
12:11 sudshekhar02 joined #evergreen
12:12 yboston there is an issue that always comes up the very ifrst time you connect the EG cleint to a EG server
12:12 yboston it might be happening this time too
12:12 yboston what does the client say right below the button called "re-test server"
12:12 yboston does it say "200: Ok"
12:12 yboston in greeen?
12:13 snigdha26 yboston: status: 200 ok
12:13 yboston it says 200 OK once or twice?
12:13 snigdha26 yboston: twice. For status and version both
12:14 yboston OK, that is good
12:14 kmlussier snigdha26: Which demo server are you using?
12:14 snigdha26 kmlussier: demo.evergreencatalog.com
12:16 kmlussier Hmmmm...I'm getting the same error when I try registering a workstation on that server.
12:16 yboston snigdha26: let me try it on my computer to see if I see the same problem. need to ddownload cleitn software first, etc
12:18 snigdha26 yboston: Im behind a proxy server. That wouldn't make a difference right?
12:18 kmlussier snigdha26: No, I don't think it's you. There seems to be a problem with that server right now.
12:18 yboston that could make a difference, but I just got a network erro too
12:18 yboston *error
12:18 yboston and I am not using a proxy
12:20 kmlussier I don't know if anyone from ESI has time to look at a problem with the demo server, but the error I get when trying to register a workstation is http://pastebin.com/M2uV90Td
12:20 yboston I think there is something wrong with that community server
12:20 bshum snigdha26: Actually proxy servers can sometimes interfere with Evergreen functionality.  But it sounds like there is still something wrong with that server.
12:20 kmlussier snigdha26: In the meantime, you might want to try the MassLNC demo server.
12:24 snigdha26 kmlussier: I tried doing that but Im unable to open that page.
12:24 * kmlussier checks.
12:25 snigdha26 The server isn't responding. the link times out
12:26 kmlussier :(
12:26 wsmoak left #evergreen
12:26 kmlussier snigdha26: OK, I can get that one back up and running for you. But it takes about 10 to 15 minutes. Sorry about that.
12:27 snigdha26 kmlussier: Not a problem :)
12:27 yboston snigdha26: this is good that you are helping us test our test community servers, thanks!
12:28 snigdha26 yboston: haha, just trying to get started
12:29 kmlussier yboston: Better to find the problems now than in the middle of Friday's DIG hackfest, right? :)
12:29 yboston kmlussier: exactly
12:30 snigdha26 yboston: what's the hackfest about?
12:32 yboston the Evergreen community has a group called DIG (Docuemntation Interest Group) that kmlussier and I are part of. This Friday, September 12 we are having a DIG hack-a-way.
12:32 kmlussier snigdha26: The 2.7 release of Evergreen will be out later this month. The goal of this hack-a-way is to try to finish documenting our new 2.7 features.
12:32 yboston On that day memebrs of DIG and new volunteers will spend a whole day wproking on documentation
12:35 snigdha26 yboston, kmlussier: That sounds great! I'll try to get familiar with the software till then. Would love to help out
12:37 yboston snigdha26: that would be great
12:38 yboston snigdha26: we can help answer questions this week in preparation for Friday or for contributing any other day
12:40 kmlussier Speaking of OPW, does anyone have the tuits to look through the LP bugs and identify any new bitesize bugs that may have been filed since the last time we were doing something like this? I looked at them, but I don't have a good handle on which bugs are easy fixes and which are more complicated.
12:41 sudshekhar02 joined #evergreen
12:42 snigdha26 yboston: I would have to work on asciidoc right?
12:42 yboston snigdha26: no that is optional
12:43 kmlussier snigdha26: The masslnc community demo server should be ready now.
12:47 snigdha26 kmlussier: There's an error testing the hostname
12:48 yboston snigdha26: any errors in the are below "re-test server"?
12:48 yboston *area
12:48 kmlussier snigdha26: you might need to add an SSL exception for that server.
12:49 snigdha26 yboston, kmlussier: All good, I was able to register :D
12:50 kmlussier snigdha26: Was it the SSL exception? If so, I should add that info to the wiki page.
12:50 snigdha26 kmlussier: yes, it needs the SSl exception
12:51 kmlussier snigdha26: ok, thanks! And good luck!
12:52 snigdha26 kmlussier: thanks a lot !
12:56 nhilton joined #evergreen
12:57 snigdha26 kmlussier, yboston: How can I go about fixing the bugs reported on http://bit.ly/YqlB8y
13:04 _bott_ joined #evergreen
13:04 yboston snigdha26: it depends on the bug. One bug mentions that there is a bad link on a part of the documentation
13:05 yboston you would need to find the locaiton of the bad link, copy the bad docuemntation section, and re-write it with the corect URL, then submit the corrected text to the DIG maling list
13:07 yboston it might be easier to start with the new features for 2.7 that we need to document on Friday. A couple of them are very simple with little work to do, but good for practice
13:07 kmlussier snigdha26: Have you looked at the guidelines at http://evergreen-ils.org/dokuwiki/doku.php?id=e​vergreen-docs:how-to-contribute-documentation?
13:07 snigdha26 yboston: same goes for say, the formatting bug? Re-write the documentation and submit on the mailing list?
13:09 yboston one catch is that, on some bugs, you need to fix AsciiDoc. on other bugs you don't. when providing new documentation it is optional to use AsciiDoc
13:10 kmlussier snigdha26: So for that bug, remingtron provided links to the files where there are formatting bugs. If you look at the intermediate instructions on that page, it talks about how you can make edit to the files in github.
13:11 buzzy joined #evergreen
13:11 snigdha26 yboston: so for the 2.7 version http://wiki.evergreen-ils.org/dok​u.php?id=evergreen-docs:2.7_needs these are the features to be worked on?
13:12 snigdha26 kmlussier: Can I do that even though Im only a beginner? Or should I use the mailing list first?
13:12 yboston snigdha26: exactly
13:13 yboston my name is "Yamil" and I assigned two extremely simple tasks for 2.7 that would be good for learning the basics of contribtuting
13:14 yboston I meant to say I assinged myself two simple tasks, and I am looking to team up with a new volunteer.
13:14 kmlussier snigdha26: I would try it as a first step. The edits there don't make it into the live documentation. You'll still need to send an e-mail to the list to have it reviewed before it makes it into the documentation.
13:15 yboston snigdha26: I need to get some lunch now, but I will be back at my computer in 30 minutes. You can also try to reach me tomorrow on IRC as yboston
13:16 snigdha26 kmlussier: alright, I'll use the mailing list then
13:16 kmlussier gmcharlt: Huh. I can't believe I've made it along this far in life without realizing ZIP is an acronym.
13:17 gmcharlt kmlussier: gotta improve those zones!
13:17 snigdha26 yboston: Please let me what I would have to do to help with the tasks you have
13:42 sudshekhar joined #evergreen
14:04 nhilton joined #evergreen
14:25 yboston snigdha26: are you still on the IRC channel?
14:26 snigdha26 yboston: yes, still here
14:27 snigdha26 I submitted the patches to fix the bugs reported here https://bugs.launchpad.net/evergreen/+bug/1294269
14:27 pinesol_green Launchpad bug 1294269 in Evergreen "Small documentation formatting bugs" (affected: 1, heat: 6) [Low,New]
14:29 yboston Very good, where did you put the changes? I don't see an attachment to the email  you sent to the DIG mailing list
14:29 yboston did you make the changes on Github?
14:30 snigdha26 yboston: I made the changes on the files on github itself
14:31 yboston I see it now
14:36 yboston this is a good start
14:37 yboston I have helped other volunteers that have used Github to make changes thourgh "forking" and "pull requests". I don't think you used that approach, but i could be wrong.
14:37 yboston I have not helped anyone usign your method of editing directly on Gihub without doing a fork. I know there is a way to move your cahnges to the main EG repository by just using the Github site, but I am not sure how.
14:37 snigdha26 yboston: can i know more about the tasks on Cataloging and OPAC that are under you?
14:38 yboston I know a more complicated way of getting you changes in using Git on my computer's command line
14:38 snigdha26 yboston: I haven't really worked on Github before this
14:38 yboston snigdha26: it is good you have started with Github
14:39 snigdha26 I just followed the instructions on the 'How to contribute' page
14:39 yboston the EG community is trying to use it more and more, the DIG group is still learning how to use it for docuemntation
14:40 snigdha26 should I be using the method you mentioned?
14:40 yboston Github should be a lot easier, I just need to learn a few things first
14:40 yboston we want more people to sue Github
14:40 yboston *use
14:41 yboston I need to read those intructions for Github on the DIG page, they have been changes since the last time I read them. hold on
14:43 snigdha26 I wasn't sure about how to make changes for the other bugs since I couldn't find the relevant link on the github site
14:54 yboston I read the Github suggestions in the DIG pages, but I am still not sure how to move your cahnges by just using the Github site. Let me send an emial to another DIG member for help. At the latest by Wednesday I will have added your cahnges by the Github site or I will use Git on my computer.
14:56 snigdha26 yboston: Sure :) I'll figure out how to use git by then
15:06 yboston I sent out the email to remingtron to see what he thinks. In the meantime, it might help for you to cick the "fork" button for the EG repository to more easily make changes right from Github
15:06 yboston https://github.com/evergree​n-library-system/Evergreen
15:07 akilsdonk_ joined #evergreen
15:07 yboston Git can be tricky to learn at first, so you might want to stick to Github for the first couple of weeks.
15:11 kmlussier joined #evergreen
15:16 remingtron yboston: it looks like snigdha26 already "forked" the repo on github
15:17 remingtron but maybe didn't submit pull requests for their commits
15:18 snigdha26 remingtron: Hi, yea I didn't pull requests
15:18 yboston there might be another step she has to take on Github so we can properly see her change
15:18 remingtron snigdha26: could you create a pull request for each of your changes? Github makes this pretty easy.
15:19 remingtron that makes it easier for us to include your changes in the master repository
15:19 buzzy joined #evergreen
15:23 snigdha26 remingtron: I'll do that
15:43 dreuther joined #evergreen
15:51 sarabee joined #evergreen
15:52 whargrove joined #evergreen
15:53 mrpeters left #evergreen
15:53 ericar joined #evergreen
15:54 whargrove Hi all, where can I get some documentation on sending SIP2 commands to an evergreen server?
16:05 RoganH joined #evergreen
16:14 b_bonner joined #evergreen
16:15 berickm joined #evergreen
16:20 whargrove left #evergreen
16:30 snigdha26 remingtron: I made the changes and pulled requests for them
16:30 tspindler left #evergreen
16:34 gsams joined #evergreen
16:37 yboston snigdha26: I can see you cahnges on your Github page now
16:37 yboston was there a button called "propose" or "pull request" that you pressed?
16:39 snigdha26 yboston: At first, after making the changes, I proposed the changes and then on the next page, there was an option for 'pull request'
16:39 snigdha26 I hadn't pressed the 'pull request' last time
16:40 snigdha26 Sorry, was a little confused
16:48 yboston no worries, I am learning too
16:48 yboston about Github
16:48 yboston I will add your changes tomorrow
16:50 snigdha26 yboston: I was looking at the other bugs too (say the broken link in the documentation for 2.4) but I'm having trouble locating the file on github
16:58 yboston I did a search on my computer, since I have a copy of the files. Here is the file that I think needs fixing… docs/admin/acquisitions_admin.txt
16:58 yboston https://github.com/evergreen-library-system/Evergr​een/blob/master/docs/admin/acquisitions_admin.txt
17:16 BigRig_ joined #evergreen
17:16 sarabee_ joined #evergreen
17:16 mmorgan left #evergreen
17:27 geoffsams joined #evergreen
17:35 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:41 Dyrcona joined #evergreen
20:22 hbrennan joined #evergreen
23:32 ktomita_ joined #evergreen
23:36 bshum_ joined #evergreen
23:39 mtj_ joined #evergreen
23:42 jeff_ joined #evergreen
23:42 pmurray joined #evergreen

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