| Time |
Nick |
Message |
| 00:13 |
|
mcooper joined #evergreen |
| 06:37 |
|
Mark__T joined #evergreen |
| 07:30 |
|
rsinger joined #evergreen |
| 07:57 |
|
kmlussier joined #evergreen |
| 08:01 |
|
jboyer-isl joined #evergreen |
| 08:06 |
|
stevenyvr2 joined #evergreen |
| 08:06 |
|
stevenyvr2 left #evergreen |
| 08:14 |
kmlussier |
rangi++ #Providing extra details on Koha bug squashing days. |
| 08:21 |
|
ericar joined #evergreen |
| 08:24 |
|
akilsdonk_ joined #evergreen |
| 08:24 |
|
_bott_ joined #evergreen |
| 08:27 |
|
kbeswick joined #evergreen |
| 08:27 |
|
Shae joined #evergreen |
| 08:28 |
|
Dyrcona joined #evergreen |
| 08:33 |
|
rfrasur joined #evergreen |
| 09:00 |
rfrasur |
wooohooo...first payment pilot email. Go Evergreen! |
| 09:02 |
Dyrcona |
kmlussier: I also get errors when I try to renew things on my development server. I didn't try on our training server. Did you say it was happening there, too? |
| 09:03 |
kmlussier |
Dyrcona: Yes, I tried again yesterday afternoon. Can't renew anything. |
| 09:03 |
kmlussier |
I've copied the error messages, but, if you were able to reproduce it, I guess I don't need to send them along? |
| 09:03 |
Dyrcona |
Did it say the error was in Circulate.pm at line 2807? |
| 09:04 |
kmlussier |
That sounds right, but just let me double check. |
| 09:04 |
kmlussier |
Dyrcona: Yup, that's right. |
| 09:05 |
Dyrcona |
OK. It's the same error for me, too. |
| 09:05 |
|
timf joined #evergreen |
| 09:06 |
Dyrcona |
Ah ha! |
| 09:06 |
Dyrcona |
It's a bug in my void payment branch. |
| 09:06 |
Dyrcona |
But, that shouldn't be on our training server....Hmm..... |
| 09:07 |
Dyrcona |
So, it is something else. |
| 09:07 |
kmlussier |
It's happening on the training server too? |
| 09:08 |
Dyrcona |
I thought you said it was. |
| 09:08 |
kmlussier |
Dyrcona: Oh, wait, you asked me if it was happening on training. Sorry. I only use the dev server. |
| 09:08 |
* kmlussier |
apparently didn't fully read your question. |
| 09:09 |
|
collum joined #evergreen |
| 09:09 |
Dyrcona |
OK> |
| 09:10 |
Dyrcona |
I think I might have to change the code in that place to use one of the billing views, but for now I'll try something quick and dirty. |
| 09:10 |
Dyrcona |
I'll have to try our training server later. |
| 09:10 |
Dyrcona |
If the problem is what I think it is, it shouldn't be happening there. |
| 09:16 |
Dyrcona |
Throw a bandage over the wart, restart open-ils.circ, and renew a book. |
| 09:16 |
Dyrcona |
Bingo1 |
| 09:16 |
Dyrcona |
Bingo! |
| 09:16 |
kmlussier |
Dyrcona++ |
| 09:16 |
rfrasur |
Dyrcona++ |
| 09:17 |
Dyrcona |
kmlussier++ #For testing billing development without realizing it. :) |
| 09:17 |
* Dyrcona |
makes a note to do something more permanent when he gets home this evening. |
| 09:17 |
rfrasur |
kmlussier++ #for good discussion/points on bug squashing |
| 09:17 |
kmlussier |
Dyrcona: Never hurts to get an early start on testing! ;) |
| 09:18 |
Dyrcona |
I'm going to check our training server just to be sure. |
| 09:19 |
Dyrcona |
It might be something that went in recently, but I doubt it is a problem without my void payment code also being in place. |
| 09:20 |
Dyrcona |
tsbere: I think I just realized why you still use 2.3.0 as the production version. :) |
| 09:22 |
Dyrcona |
<rhetorical>I should be able to change the Name in application.ini without causing any problems?</rhetorical> |
| 09:23 |
Dyrcona |
k |
| 09:23 |
Dyrcona |
oops |
| 09:26 |
|
mrpeters joined #evergreen |
| 09:26 |
Dyrcona |
OK. As I suspected, not a problem in training. |
| 09:26 |
|
asimon joined #evergreen |
| 09:27 |
Dyrcona |
Oh! I know why I was confused. Someone reported a cataloging problem with our training server yesterday. |
| 09:29 |
asimon |
I'm installing Evergreen on a new database server running PostgreSQL 9.2. While installing the prerequisites, I get the following message: The following packages have unmet dependencies: libpq-dev: Depends: libpq5 (= 9.1.9-1~bpo60+1) but 9.2.4-1.pgdg60+1 is installed. Should I be installing Evergreen before PostgreSQL? |
| 09:30 |
Dyrcona |
asimon: I always install Postgres before installing Evergreen. |
| 09:31 |
asimon |
Dyrcona: I'm not installing OpenSRF, as it's not needed (our current database server doesn't have it). Would installing the OpenSRF prerequisites first solve this problem? |
| 09:32 |
Dyrcona |
asimon: Not that specific problem, no. |
| 09:32 |
Dyrcona |
asimon: What distro are you installing onto? |
| 09:33 |
asimon |
Dyrcona: Debian Squeeze |
| 09:33 |
Dyrcona |
asimon: Have a look at this: http://wiki.postgresql.org/wiki/Apt |
| 09:34 |
Dyrcona |
I use those repose for PostgreSQL, and not the distro repos. |
| 09:34 |
Dyrcona |
s/repose/repos/ |
| 09:34 |
dbs |
asimon: squeeze? yeesh. why not wheezy? |
| 09:35 |
asimon |
dbs: I'd love to, except that Evergreen doesn't yet support Wheezy (at least not officially). |
| 09:36 |
Dyrcona |
asimon: Wheezy support is official, at least in master/2.5, if not also 2.4. |
| 09:36 |
asimon |
Dyrcona: It's not in 2.4.1 |
| 09:36 |
dbs |
asimon: yeah, I'm sure 2.4 supports wheezy officially |
| 09:37 |
csharp |
distro upgrades are always messy |
| 09:37 |
csharp |
(with EG, that is) |
| 09:37 |
Dyrcona |
Linux From Scratch! |
| 09:37 |
bshum |
Err, I don't think 2.4 has those patches. Wasn't berick still working on breaking up things into separate makefiles? |
| 09:37 |
csharp |
Dyrcona++ |
| 09:37 |
bshum |
(2.5/master either for that matter) |
| 09:37 |
|
mmorgan joined #evergreen |
| 09:37 |
bshum |
I know we added Wheezy support for OpenSRF's side of things |
| 09:37 |
csharp |
bshum: I was working on ubuntu when I got stalled on the 12.04 file |
| 09:38 |
csharp |
so that may be the hold-up on the per-distro makefile stuff :-/ |
| 09:38 |
Dyrcona |
Though I use Ubuntu, I'm really starting to dislike it in a serious way. |
| 09:38 |
asimon |
bshum: Yes, OpenSRF 2.2.0 supports Wheezy. |
| 09:38 |
csharp |
Dyrcona: what issues are you seeing? |
| 09:38 |
bshum |
csharp: That and testing for some of us :( |
| 09:38 |
|
krvmga joined #evergreen |
| 09:39 |
Dyrcona |
csharp: Frequently busted packages that stay busted, among other things. |
| 09:39 |
csharp |
hmm |
| 09:39 |
Dyrcona |
I also think Canonical is turning into Apple. |
| 09:39 |
krvmga |
here is the result for an individual item in our catalog http://bark.cwmars.org/eg/opac/record/2614962?query=avatar;qtype=keyword;locg=1;expand=marchtml#marchtml |
| 09:39 |
bshum |
Dyrcona: The yaz thing happened in Lucid too, once upon a time. |
| 09:39 |
bshum |
Broken yaz I mean |
| 09:39 |
csharp |
Dyrcona: yeah - that gives me qualms too |
| 09:39 |
Dyrcona |
bshum: More support for my argument. :) |
| 09:40 |
bshum |
Dyrcona++ |
| 09:40 |
asimon |
Dyrcona: I installed PostgreSQL 9.2 from http://wiki.postgresql.org/wiki/Apt |
| 09:40 |
* csharp |
has bounced back to Fedora on his main desktop for reasons like Canonical <-> Apple |
| 09:40 |
krvmga |
The title shows as Avatar [videorecording] |
| 09:40 |
Dyrcona |
asimon: Good. Have you also installed libpq-dev from there? |
| 09:41 |
krvmga |
that [videorecording] bit is from MARC 245 h |
| 09:41 |
dbs |
asimon: hmm, wheezy support for Evergreen should be a high-priority bug then :/ |
| 09:41 |
dbs |
good old GMD |
| 09:41 |
dbs |
csharp++ |
| 09:41 |
krvmga |
i haven't found the code that tells the system to display that subfield in this title line |
| 09:41 |
krvmga |
anyone know where it is? |
| 09:41 |
csharp |
krvmga: try misc_util.tt2? |
| 09:41 |
asimon |
dbs: Yes, I agree. I have created the load balancer and logger servers using Wheezy, since they don't need Evergreen. |
| 09:42 |
bshum |
https://bugs.launchpad.net/evergreen/+bug/1190279 |
| 09:42 |
pinesol_green |
Launchpad bug 1190279 in Evergreen "Modularize Makefile.install" (affected: 3, heat: 16) [Wishlist,In progress] |
| 09:42 |
Dyrcona |
k |
| 09:42 |
Dyrcona |
grr... |
| 09:42 |
krvmga |
csharp: that was my first thought. not there. |
| 09:42 |
* Dyrcona |
still working on focus-follows-brain for X. |
| 09:42 |
dbs |
bshum: yes, but... refactoring Makefile.install should be completely separate from "Do we officially support wheezy now?" |
| 09:42 |
krvmga |
which tt2 file is displaying this data? |
| 09:43 |
bshum |
dbs: Oh in that case, it's the old dupe bug 1014724 |
| 09:43 |
pinesol_green |
Launchpad bug 1190279 in Evergreen "duplicate for #1014724 Modularize Makefile.install" (affected: 3, heat: 16) [Wishlist,In progress] https://launchpad.net/bugs/1190279 |
| 09:43 |
bshum |
Which blah |
| 09:43 |
bshum |
Points the wrong way |
| 09:43 |
bshum |
I tested berick's code for supporting wheezy now, but it used more CPAN than packages so I wanted to poke it further. |
| 09:43 |
* dbs |
kind of hates when new bugs live on, and the old bugs get closed as a duplicate. a bit. |
| 09:43 |
asimon |
Dyrcona: Yes, "libpq-dev is already the newest version." |
| 09:44 |
dbs |
kind of gives a false view of history. |
| 09:44 |
dbs |
krvmga: what version of Evergreen? |
| 09:44 |
csharp |
asimon: what does 'apt-cache policy libpq-dev' tell you? |
| 09:44 |
krvmga |
dbs: 2.3 |
| 09:44 |
dbs |
libpq and libpq-dev are different packages anyway, right? |
| 09:45 |
bshum |
dbs: I only do that if the new bug has better information in it (or an actual patch). But yes, bug tracking is unwieldy :( |
| 09:45 |
asimon |
csharp: Installed: 9.2.4-1.pgdg60+1 |
| 09:45 |
krvmga |
i was looking in /openils/var/templates/opac/parts/record because i thought one of the files there did it |
| 09:45 |
csharp |
krvmga: parts/misc_util.tt2:45: titsubs = xml.findnodes('//*[@tag="245"]/*[(@code) and (@code != "6") and (@code != "8")]'); |
| 09:46 |
bshum |
It should be in misc_util |
| 09:46 |
bshum |
Yeah, csharp++ |
| 09:46 |
csharp |
line 45 of misc_util.tt2 (in case that's not readable) |
| 09:46 |
dbs |
krvmga: yeah, you can look at Open-ILS/src/templates/opac/parts/record/summary.tt2 and find that it displays attrs.title_extended - which is defined in misc_utils.tt2, as csharp is pointing at |
| 09:46 |
dbs |
s/s// |
| 09:46 |
krvmga |
csharp++ |
| 09:46 |
krvmga |
dbs++ |
| 09:46 |
krvmga |
thanks :) |
| 09:47 |
asimon |
csharp: The version table shows 9.2.4-1.pgdg60+1, 9.1.9-1~bpo60+1, 8.4.17-0squeeze1, 8.4.15-0squeeze1 (in that order). |
| 09:47 |
csharp |
found with 'grep -rn 245 *' in Open-ILS/src/templates/opac, btw |
| 09:47 |
krvmga |
i saw attrs.title_extended there and that's when i got lost |
| 09:48 |
krvmga |
grep. so useful. |
| 09:48 |
bshum |
title_extended is used in the full record details, the other shorter one is used in search results. |
| 09:49 |
csharp |
asimon: hmm - I wonder why it's not depending on the 9.2 version of libpq5 |
| 09:49 |
krvmga |
why i was looking for this code is that i want to display 245 h in the short returns and i thought this would show me how to do it. |
| 09:49 |
csharp |
what about 'apt-cache policy libpq5'? |
| 09:49 |
dbs |
krvmga: heh, then you're looking for the args.title definition, which only wants a b n p. You can add h to it. |
| 09:50 |
krvmga |
dbs: i saw that and wondered if i could do that...or if i would break it by doing so |
| 09:50 |
dbs |
Or change the results page to show args.title_extended instead |
| 09:50 |
asimon |
csharp: Installed: 9.2.4-1.pgdg60+1, with the same versions as libpq-dev in the version table. |
| 09:50 |
csharp |
ok |
| 09:50 |
bshum |
Just add h. The whole title is lengthy and would drive me insane :) |
| 09:51 |
krvmga |
dbs: thanks. i'm going to give it a shot. it has the virtue of being easily reversible. |
| 09:51 |
asimon |
csharp: Installing Evergreen before PostgreSQL 9.2 would solve this problem, no? |
| 09:51 |
* berick |
wonders where csharp got w/ his ubuntu experiment for bug #1190279 |
| 09:51 |
pinesol_green |
Launchpad bug 1190279 in Evergreen "Modularize Makefile.install" (affected: 3, heat: 16) [Wishlist,In progress] https://launchpad.net/bugs/1190279 |
| 09:51 |
csharp |
asimon: I think this is an APT level problem and that shouldn't matter (theoretically) |
| 09:52 |
|
yboston joined #evergreen |
| 09:53 |
csharp |
berick: my branch is here: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/csharp/ubuntu-per-distro-makefile - I got stalled out when CPAN was breaking on the 12.04 install |
| 09:53 |
csharp |
berick: I've been assuming the error is mine and when I spent a couple of hours trying to find it, I lost steam :-/ |
| 09:54 |
csharp |
10.04 installed okay in my test |
| 09:54 |
csharp |
my test only extended to seeing if the Makefile.install script finished without errors |
| 09:55 |
csharp |
asimon: interesting, I don't see a 9.2 branch here: http://apt.postgresql.org/pub/repos/apt/pool/ |
| 09:56 |
berick |
csharp: gotcha, thanks for the recap. i'll try to carve out a chunk of time soon to eyeball your branch |
| 09:56 |
berick |
would be nice to get these in |
| 09:56 |
csharp |
berick: thanks - I'll look again too |
| 09:57 |
asimon |
csharp: http://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-9.2 |
| 09:58 |
Dyrcona |
csharp: This is where you need to look: http://apt.postgresql.org/pub/repos/apt/dists/squeeze-pgdg/ |
| 09:58 |
|
mcooper joined #evergreen |
| 09:59 |
asimon |
csharp: The Evergreen prerequisite installation wants the backport repo to install the PostgreSQL 9.1 client. Would eliminating the backport repo fix the problem, since PostgreSQL 9.2 client is already installed with the PostgreSQL 9.2 install? |
| 10:00 |
dbs |
asimon: quite possibly. IIRC, there had been some question about PostgreSQL 9.2 support leading up to the 2.4 release, but AFAIK there's nothing preventing 9.2 from actually working |
| 10:00 |
Dyrcona |
dbs asimon: 9.2 works we've used it in our training and development servers. |
| 10:01 |
asimon |
dbs: Equinox Support has blessed PostgreSQL 9.2. |
| 10:01 |
* dbs |
seems to recall suggesting at some point that we make very clear statements about what distros / major dependencies are officially supported for particular releases as a standard process thing |
| 10:02 |
dbs |
Dyrcona: yeah, I've been using 9.2 on Fedora for a few months now too. but I don't hit all the pieces of Evergreen in my day-to-day testing |
| 10:06 |
csharp |
asimon: ah - I didn't look in /main |
| 10:07 |
asimon |
csharp: Note that Dyrcona has provided a different repo. |
| 10:08 |
csharp |
Dyrcona: asimon: thanks - getting my head turned around |
| 10:10 |
csharp |
asimon: I'm assuming you've done 'sudo apt-get update' and 'sudo apt-get -f install', yes? |
| 10:12 |
asimon |
csharp: Yes. I just uninstalled PostgreSQL 9.2 and the Evergreen installation is proceeding normally. I will reinstall PostgreSQL 9.2 after the Evergreen install. |
| 10:12 |
csharp |
ok - hope that works! |
| 10:17 |
asimon |
csharp: TY |
| 10:20 |
eeevil |
asimon: 9.2 is fine (though ESI can't and doesn't bless anything for the project, beyond confirming it works), so to be clear about the state of play, your problem is orthogonal to runtime compatability. the prereq installer for debian uses apt, and debain-distributed versions available just don't include 9.2 in a way that the automated process can handle as it's currently written |
| 10:21 |
eeevil |
@later tell asimon 9.2 is fine (though ESI can't and doesn't bless anything for the project, beyond confirming it works), so to be clear about the state of play, your problem is orthogonal to runtime compatability. the prereq installer for debian uses apt, and debain-distributed versions available just don't include 9.2 in a way that the automated process can handle as it's currently written |
| 10:21 |
pinesol_green |
eeevil: The operation succeeded. |
| 10:22 |
eeevil |
@later tell asimon the choice comes down to using the prereq installer to make things easy, or installing prereqs by hand to get the exact versions you want |
| 10:22 |
pinesol_green |
eeevil: The operation succeeded. |
| 10:23 |
|
Pibbits joined #evergreen |
| 10:23 |
eeevil |
(tossing that out here publicly for all to benefit, to whatever degree there may in fact be a benefit) |
| 10:24 |
rfrasur |
eeevil++ |
| 10:39 |
|
mllewellyn joined #evergreen |
| 11:10 |
|
_zerick_ joined #evergreen |
| 11:11 |
|
zerick joined #evergreen |
| 11:11 |
kmlussier |
berick++ # bug 1207396 |
| 11:11 |
pinesol_green |
Launchpad bug 1207396 in Evergreen "Patron self-registration form" (affected: 1, heat: 6) [Wishlist,In progress] https://launchpad.net/bugs/1207396 - Assigned to Bill Erickson (erickson-esilibrary) |
| 11:16 |
paxed |
that needs a CAPTCHA |
| 11:16 |
|
dboyle joined #evergreen |
| 11:19 |
mcooper |
berick++ too -- that looks great |
| 11:20 |
krvmga |
this is just a report back. in misc_util.tt2 adding the code -- or @code="h" -- to line 37 did not break anything and got me the GMD display in the title that i was looking for. |
| 11:21 |
pinesol_green |
[evergreen|Jason Etheridge] Eliminate a warning in Z3950.pm - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=e455913> |
| 11:21 |
pinesol_green |
[evergreen|Jason Etheridge] Test for an MFHD warning in 14-OpenILS-Utils.t - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=11f04ea> |
| 11:21 |
krvmga |
just for sanity, in my misc_util.tt2, i also changed line 36 'abmp' to 'abhmp' |
| 11:22 |
berick |
nc_cardinal++ # bug 1207396 |
| 11:22 |
pinesol_green |
Launchpad bug 1207396 in Evergreen "Patron self-registration form" (affected: 1, heat: 6) [Wishlist,In progress] https://launchpad.net/bugs/1207396 - Assigned to Bill Erickson (erickson-esilibrary) |
| 11:22 |
rfrasur |
berick: anyone else: Did Grand Rapids do something similar? |
| 11:23 |
bshum |
rfrasur: That's what I was just thinking to myself. That bott or jeff might have written something like that locally. |
| 11:23 |
jeff_ |
yeah, we have that. |
| 11:23 |
* bshum |
vaguely recalls seeing a lightning talk or presentation like that. |
| 11:23 |
jeff_ |
tadl.org/newuser |
| 11:24 |
jeff_ |
saves a lot of time and errors in-house, also gets used externally. |
| 11:24 |
jeff_ |
uses the pending / staging user tables. |
| 11:24 |
rfrasur |
yes...and they hooked up a way to capture patron signatures (though I can't remember why right now...even though it was important) |
| 11:24 |
|
acoomes joined #evergreen |
| 11:25 |
pinesol_green |
[evergreen|Jason Etheridge] The check library for Debian and Fedora - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=ace3d99> |
| 11:25 |
pinesol_green |
[evergreen|Jason Etheridge] C unit test examples for Evergreen - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=33b6b48> |
| 11:25 |
egbuilder |
build #268 of evergreen-master-ubuntu-12.04-x86 is complete: Failure [failed test] Build details are at http://testing.evergreen-ils.org/buildbot/builders/evergreen-master-ubuntu-12.04-x86/builds/268 blamelist: Jason Etheridge <jason esilibrary.com> |
| 11:25 |
egbuilder |
build #234 of evergreen-master-fedora-18 is complete: Failure [failed test] Build details are at http://testing.evergreen-ils.org/buildbot/builders/evergreen-master-fedora-18/builds/234 blamelist: Jason Etheridge <jasonesilibrary.com> |
| 11:26 |
egbuilder |
build #292 of evergreen-master-debian-6.00-x86_64 is complete: Failure [failed test] Build details are at http://testing.evergreen-ils.org/buildbot/builders/evergreen-master-debian-6.00-x86_64/builds/292 blamelist: Jason Etheridge <jasonesilibrary.com> |
| 11:26 |
phasefx |
ruh roh |
| 11:26 |
rfrasur |
jeff_: Do your libraries require picture ID? |
| 11:26 |
graced |
jeff_: neat! Where's the commit for that patron self-reg? |
| 11:26 |
jeff_ |
rfrasur: signatures is a grpl thing, we don't do that here. |
| 11:27 |
* csharp |
checks on those buildslaves |
| 11:27 |
paxed |
jeff_: have you ever been spammed by bots via that form? |
| 11:27 |
rfrasur |
right...I was thinking that was bott |
| 11:27 |
* paxed |
is leery of leaving any kind of form that adds data to the database open without any kind of captcha. |
| 11:28 |
rfrasur |
paxed: it's not difficult to add that though, right? |
| 11:28 |
eeevil |
phasefx: no worries. buildslaves just need Test::Warn installed, it looks like |
| 11:28 |
csharp |
ubuntu and fedora slaves look ok |
| 11:29 |
bshum |
buildbot++ |
| 11:29 |
paxed |
rfrasur: nah. i've even rolled my own captchas for some small sites. |
| 11:29 |
phasefx |
eeevil: same conclusion I came to, phew :) |
| 11:29 |
csharp |
eeevil: I can install those |
| 11:29 |
csharp |
on ubuntu & fedora (don't have the debian one) |
| 11:29 |
bshum |
phasefx++ too |
| 11:29 |
jeff_ |
graced: there's a pair of bugs, and the self-reg app is a distinct bit of code which I need to put in a public repo. |
| 11:29 |
rfrasur |
paxed: thought so. |
| 11:29 |
jeff_ |
graced: but point taken. :-) |
| 11:29 |
bshum |
csharp: I think dbs has the debian ones |
| 11:29 |
dbs |
captcha-- # accessibility loss |
| 11:30 |
rfrasur |
jeff_++ berick++ |
| 11:30 |
jeff_ |
paxed: not yet. we did have a captcha, but removed it for usability. :-) |
| 11:30 |
paxed |
dbs: not necessarily. |
| 11:30 |
* dbs |
will go poke the slaves that need new deps |
| 11:30 |
dbs |
paxed: just usually. |
| 11:30 |
paxed |
dbs: right |
| 11:31 |
jeff_ |
our original app prototype was more full-featured -- did checks to see if the patron existed, and if they did not exist and they provided us with their drivers license, auto-created the patron immediately. |
| 11:31 |
graced |
jeff_: Just curious if we'd missed it - not trying to call you out or anything. |
| 11:32 |
jeff_ |
graced: i call out others on that. please don't hesitate to call me out. :-) |
| 11:33 |
Dyrcona |
bshum: Looks like OFTC doesn't like anybody today. :) |
| 11:33 |
graced |
jeff_: Meh, I make at least a dozen mistakes a day, I have no ground to call others out. |
| 11:34 |
bshum |
Dyrcona: It's a sign! |
| 11:35 |
Dyrcona |
Time to take up potato farming! |
| 11:35 |
|
jdouma joined #evergreen |
| 11:35 |
egbuilder |
build #293 of evergreen-master-debian-6.00-x86_64 is complete: Success [build successful] Build details are at http://testing.evergreen-ils.org/buildbot/builders/evergreen-master-debian-6.00-x86_64/builds/293 |
| 11:36 |
berick |
jeff_: if you have the time and feel like eyeballing my design doc for self-reg, i'd appreciate any input/suggestions you might have. real_world_experience++ |
| 11:37 |
pinesol_green |
[evergreen|Jason Etheridge] pgTAP examples - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c36c86e> |
| 11:37 |
pinesol_green |
[evergreen|Galen Charlton] start adding pgTAP test cases - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=bb98f3f> |
| 11:37 |
pinesol_green |
[evergreen|Galen Charlton] use .pg extension for pgTAP test cases - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=97983b6> |
| 11:37 |
pinesol_green |
[evergreen|Galen Charlton] add regression test for LP#1155329 - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=bd4d765> |
| 11:37 |
pinesol_green |
[evergreen|Jason Etheridge] Use the .pg extension - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=7e8eec6> |
| 11:37 |
egbuilder |
build #270 of evergreen-master-ubuntu-12.04-x86 is complete: Success [build successful] Build details are at http://testing.evergreen-ils.org/buildbot/builders/evergreen-master-ubuntu-12.04-x86/builds/270 |
| 11:38 |
dbs |
phasefx et al: the test failures for buildbot are a good note to project-self that new prereqs should be called out in a specific section in release notes |
| 11:38 |
|
Rish joined #evergreen |
| 11:38 |
eeevil |
dbs: agreed |
| 11:38 |
phasefx |
dbs: sounds good |
| 11:39 |
Dyrcona |
So a specific section in release notes headed something like New Prerequisites? |
| 11:39 |
Dyrcona |
Just wanting to make sure I understood correctly? |
| 11:40 |
dbs |
Dyrcona: yes, or "Upgrading notes" or something like that |
| 11:40 |
berick |
we use "Upgrad No.. |
| 11:40 |
berick |
heh |
| 11:40 |
eeevil |
Dyrcona: that's what I was thinking, too. next to the other directory-based sections, since there will be different layers/types of prereqs |
| 11:40 |
Dyrcona |
OK. Works for me with either name. |
| 11:41 |
eeevil |
well, I should clarify that. I was thinking what I said /after/ Dyrcona mentioned a separate section... |
| 11:41 |
dbs |
"Upgrade notes" -> "New prerequisites" subsection, perhaps. |
| 11:41 |
csharp |
okay - I installed Test::Warn from respective distro repos and did general updates/reboots on fedora and ubuntu buildslaves |
| 11:42 |
dbs |
csharp: cool, resubmitted build |
| 11:43 |
egbuilder |
build #237 of evergreen-master-fedora-18 is complete: Success [build successful] Build details are at http://testing.evergreen-ils.org/buildbot/builders/evergreen-master-fedora-18/builds/237 |
| 11:43 |
dbs |
csharp++ |
| 11:44 |
csharp |
dbs: let me know if you'd like to either upgrade this one to F19 or build a separate F19 server |
| 11:45 |
pinesol_green |
[evergreen|Jason Etheridge] make-pgtap-tests.pl - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d6ec452> |
| 11:45 |
dbs |
csharp: IMO, whenever you want to upgrade to F19. no rush :) |
| 11:45 |
csharp |
ok - understood |
| 11:46 |
bshum |
Dyrcona: tsbere: If either of you have time to poke again at bug 1204273, please do. Hoping to unbreak master in those areas. |
| 11:46 |
pinesol_green |
Launchpad bug 1204273 in Evergreen "bugs introduced with making state not required" (affected: 1, heat: 6) [High,Confirmed] https://launchpad.net/bugs/1204273 |
| 11:46 |
gmcharlt |
eeevil: you do realize that I now need to add a test case to catch instances of the misspelling "Moar"? ;) |
| 11:47 |
* csharp |
installs Test::Moar on the buildslaves too |
| 11:47 |
gmcharlt |
csharp++ |
| 11:47 |
csharp |
I CAN HAZ UNIT TESTZ? |
| 11:48 |
rfrasur |
csharp++ |
| 11:51 |
Dyrcona |
bshum: We'll have a look after lunch. Had a staff meeting this morning. |
| 11:51 |
bshum |
lunch++ |
| 11:52 |
rfrasur |
what's that? |
| 11:55 |
csharp |
@praise lunch |
| 11:55 |
* pinesol_green |
lunch is kind and patient to newbies |
| 11:56 |
csharp |
@praise |
| 11:56 |
pinesol_green |
csharp: (praise [<channel>] [<id>] <who|what> [for <reason>]) -- Praises <who|what> (for <reason>, if given). If <id> is given, uses that specific praise. <channel> is only necessary if the message isn't sent in the channel itself. |
| 11:57 |
eeevil |
@praise lunch for being tasty |
| 11:57 |
* pinesol_green |
lunch is the very model of a modern major hacker for being tasty |
| 11:59 |
|
acoomes_ joined #evergreen |
| 11:59 |
rfrasur |
hmm, I shall have to experiment with said lunch since pinesol has such a glowing report. |
| 12:01 |
|
jihpringle joined #evergreen |
| 12:17 |
|
mcooper joined #evergreen |
| 12:24 |
|
mcooper joined #evergreen |
| 13:34 |
|
gsams joined #evergreen |
| 13:44 |
|
_zerick_ joined #evergreen |
| 13:44 |
rfrasur |
Is there a DIG meeting at 2 EDT? |
| 13:44 |
yboston |
rfrasur: yes |
| 13:45 |
rfrasur |
rock on |
| 13:46 |
yboston |
rfrasur: for the record, I am normally not very active on IRC, but I set up my IRC client with a list of words I want to know if they are mentioned. "DIG" is one of them |
| 13:46 |
rfrasur |
I figured as much ;) |
| 13:48 |
|
stevenyvr2 joined #evergreen |
| 13:54 |
jeff_ |
cool. we're live on the state resource sharing system with ncip using iNCIPit as the responder. |
| 13:55 |
rfrasur |
jeff_++ #that's excellent. Good job on all that :D |
| 13:56 |
yboston |
heads up, the DIG monthly meeting will start at 2 PM EST |
| 13:59 |
|
agoben joined #evergreen |
| 14:00 |
|
dagreen joined #evergreen |
| 14:00 |
yboston |
#startmeeting 2013-08-01 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting. |
| 14:00 |
pinesol_green |
Meeting started Thu Aug 1 14:00:41 2013 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 '2013_08_01___dig_monthly_meeting_evergreen_documentation_interest_group__dig__monthly_meeting_' |
| 14:01 |
yboston |
The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meeting_20130801-agenda |
| 14:01 |
yboston |
#topic Introductions |
| 14:01 |
yboston |
Please feel free to start introducing yourselves... |
| 14:01 |
* yboston |
is Yamil Suarez @ Berklee college of Music - DIG meetings facilitator |
| 14:02 |
* rfrasur |
is Ruth Frasur @ Hagerstown Public Library - Evergreen Indiana |
| 14:02 |
* kmlussier |
is Kathy Lussier, MassLNC |
| 14:02 |
dagreen |
David Green, NC Cardinal |
| 14:03 |
|
kbutler joined #evergreen |
| 14:04 |
yboston |
I suspect that we will have a small gathering today |
| 14:04 |
yboston |
#topic Updates from Content Coordinators |
| 14:04 |
kmlussier |
Am I the only content coordinator here? |
| 14:05 |
|
jeff joined #evergreen |
| 14:05 |
yboston |
kmlussier: did you have something tot all about. I just saw |
| 14:05 |
yboston |
you sent an email to the lsit |
| 14:05 |
yboston |
list |
| 14:05 |
yboston |
(yes I think you are the only one) |
| 14:05 |
kmlussier |
yboston: That's not actually part of my report, but I just added it to the agenda under new business. |
| 14:05 |
kmlussier |
If we have time to get to it. |
| 14:06 |
kmlussier |
I don't have anything to report again as release coordinator, but it looks like we have a lot of discussion items under old and new business. |
| 14:06 |
yboston |
we should have time to touch on on those topics, though I wished there were more of us here |
| 14:06 |
yboston |
to join in the idscussion |
| 14:07 |
yboston |
traditionally we would go over "old business" first, but today we can start on new items |
| 14:07 |
yboston |
if you guys want |
| 14:07 |
rfrasur |
whatever you all think is best. |
| 14:08 |
yboston |
I say we go for new |
| 14:08 |
kmlussier |
+1 |
| 14:08 |
rfrasur |
+1 |
| 14:08 |
yboston |
#topic Think of ways to increase participation, create an informal survey, training during a DIG hack-a-way, or online DIG training sessions between conferences (by Yamil) |
| 14:09 |
yboston |
DIG activity has declined in the last 12 months |
| 14:09 |
yboston |
and I want to make a push for more participation |
| 14:09 |
yboston |
part of the reason why DIG participation is down |
| 14:09 |
rfrasur |
I can throw in my two cents. |
| 14:10 |
|
GHamelin joined #evergreen |
| 14:10 |
* rfrasur |
will wait |
| 14:10 |
yboston |
is because some members were going through migrations in the last 12 motnhs |
| 14:10 |
yboston |
and now some of those same members are active in the upcoming 2014 conference |
| 14:10 |
yboston |
planning |
| 14:11 |
yboston |
I want to offer some welcoming / training sessions for new members online, instead of waiting for the next conference. |
| 14:11 |
rfrasur |
great idea |
| 14:11 |
yboston |
also I guess we can try an informal survey to see what outsiders think about considering joining us |
| 14:12 |
yboston |
this issue has come up in the Evergreen Oversite Board, which I am a part of |
| 14:12 |
yboston |
we need to make it easier and more obvious for people to be able to contribute |
| 14:12 |
yboston |
in general to EG |
| 14:12 |
kmlussier |
I think that's a good idea. Also, if the training could be recorded for later streaming, people could benefit from it whenever they are available. |
| 14:13 |
yboston |
and I think documentation on general is a simple way to contribute |
| 14:13 |
yboston |
kmlussier: I totally agree |
| 14:13 |
kmlussier |
Also, I think it's a good idea to always stress that, although we prefer AsciiDoc, people can contribute in any format. |
| 14:13 |
kmlussier |
We always say that, but it can't be overstated. |
| 14:13 |
kmlussier |
rfrasur: What was your two cents? |
| 14:15 |
rfrasur |
well, speaking as someone very new to broader community and with really only the limited perspective of using Evergreen as an end-user (and some vague understanding of tech lingo), I think, like both of you, that documentation can be a great entry point for just about anyone... |
| 14:15 |
kmlussier |
I'm also interested in hearing what dagreen says as a potential new DIG member. :) BTW, welcome! |
| 14:15 |
|
rsoulliere joined #evergreen |
| 14:15 |
rfrasur |
with the understanding that there's a lot of trepidation coming into this environment |
| 14:16 |
rfrasur |
even if someone could potentially contribute a lot....just knowing how to behave...and how to get around...and who does what and what needs to be done. |
| 14:16 |
rfrasur |
It's VERY overwhelming. |
| 14:17 |
dagreen |
Thank you, kmlussier, I echo rfrasur, and intend to join your IRC meetings until I am able to actively contribute. |
| 14:18 |
GHamelin |
Hi everyone, I have just joined and have missed some of the conversation, but we are currently creating help files for version 2.4.1 |
| 14:18 |
GHamelin |
is this what people are looking for? |
| 14:18 |
dagreen |
I will be doing documentation for our end users in NC Cardinal, and figured this would be the quickest way to contribute to the larger community. |
| 14:18 |
rfrasur |
I am VERY committed to sticking with the nuts and bolts side of EG...so, I'm more willing to wade through and make mistakes and get embarrassed. There are a lot more individuals, however, who could potentially be contributing but wouldn't be able to get past all that. |
| 14:18 |
|
alexlazar joined #evergreen |
| 14:19 |
rfrasur |
GHamelin: yes...and more...and still more |
| 14:19 |
rfrasur |
dagreen++ |
| 14:19 |
GHamelin |
the current format is text with screen captures |
| 14:19 |
kmlussier |
GHamelin: I would say we're looking for anything that could fill in gaps at http://docs.evergreen-ils.org/. |
| 14:20 |
rfrasur |
that's my two cents....well, one cent. My other cent is I'm a pretty good evangelist...but I don't feel confident enough to start "spreading the gospel" of documentation at this point. |
| 14:20 |
rfrasur |
confident in my own understanding, that is |
| 14:20 |
GHamelin |
right now we are covering cataloguing, circulation, TPAC and keyboard shortcuts |
| 14:21 |
GHamelin |
we should have them complete by September |
| 14:21 |
kmlussier |
You know, I think what might help is that we don't have one clear list of what those gaps are. We have the spreadsheet from last year's DIG hackfest, and I have created a list of 2.4 features that need to be documented, but I think we might need some central clearinghosue. |
| 14:22 |
yboston |
kmlussier: I made a new version of the spreadsheet with my inter, but it is pretty messy. I can share it with you if you want. |
| 14:23 |
kmlussier |
yboston: Sure. |
| 14:23 |
rfrasur |
kmlussier: +1 - If someone just goes to that page and looks at the list...they don't know what to start picking at. |
| 14:23 |
yboston |
GHamelin: BTW, at the beginning of this meeting I just brought up that I want to increase the DIG participation by adding new members |
| 14:24 |
* rfrasur |
may not be a member |
| 14:24 |
rfrasur |
I just kinda show up places. |
| 14:24 |
dbs |
GHamelin: by "help files" you mean what gets shown when you press F1 in the staff client? |
| 14:24 |
GHamelin |
no the help link that is currently empty in the right hand corner of Evergreen |
| 14:25 |
GHamelin |
i have asked Equinox to set it up once we are done |
| 14:25 |
rfrasur |
Ah hah! |
| 14:25 |
yboston |
I never really noticed that menu there :( |
| 14:25 |
|
gdunbar joined #evergreen |
| 14:26 |
rfrasur |
me either. just gave it a try. GHamelin++ |
| 14:26 |
GHamelin |
we also wanted to contribute to the community |
| 14:26 |
rfrasur |
dbs - F1 in our staff client is check out... |
| 14:27 |
rfrasur |
(will that change?) |
| 14:27 |
yboston |
I would like to eventually steer the conversation back to bringing in new members, but I am glad to hear about StatCan's work |
| 14:27 |
GHamelin |
i don't think I am a member |
| 14:28 |
yboston |
DIG membership is a very loose concept |
| 14:28 |
GHamelin |
ok |
| 14:28 |
Dyrcona |
If DIG is like most other EG groups, all you have to do to be a member is show up. |
| 14:28 |
dagreen |
Sign me up |
| 14:28 |
yboston |
Dyrcona: exactly |
| 14:28 |
kmlussier |
You only need to show up to be a member. :) Contributions help too. |
| 14:28 |
GHamelin |
count me in |
| 14:28 |
kmlussier |
yboston: You mentioned a survey. What kind of questions would you ask? |
| 14:28 |
rfrasur |
yboston: I think the things you mentioned are a good idea. I do also like the idea of an informal survey...and wouldn't mind to start putting one together. |
| 14:28 |
GHamelin |
I have been lax in contributing to the authorities group |
| 14:29 |
GHamelin |
which i intend to start on next week |
| 14:29 |
kmlussier |
rfrasur++ |
| 14:29 |
* rfrasur |
tried to become a member of a family by showing up once - they weren't as accommodating as EG |
| 14:29 |
yboston |
you fixed some auth bugs in the code, that is plenty of help :) |
| 14:29 |
yboston |
in the survey, for example I wanted to ask what is keeping you from joining |
| 14:30 |
|
remingtron joined #evergreen |
| 14:30 |
yboston |
also, I wanted to put in questions that might actually "trick" folks into learning about us |
| 14:30 |
yboston |
though this might not be a good idea |
| 14:30 |
* rfrasur |
chuckles |
| 14:30 |
rfrasur |
I'll avoid the words "trick," "coerce," and "brainwash" |
| 14:30 |
yboston |
like "did you know that DIG membership is very informal, just need to show up: Yes / NO" |
| 14:31 |
rfrasur |
So, is the target audience people on the general listserv or is it broader? |
| 14:31 |
kmlussier |
I would say general list. |
| 14:31 |
yboston |
Instead of a survey I guess we can just send out an informative eamil asking for volunteers and soliciting suggestions from folks |
| 14:32 |
yboston |
general list or even a blog post on our homepage |
| 14:32 |
yboston |
EG home page (just a thought) |
| 14:32 |
Dyrcona |
I'd go for both the mailing list and the blog post. |
| 14:32 |
kmlussier |
yboston: I'm partial to the idea of a survey. We've done those e-mails in the past. One of the nice things about a survey is that people can be anonymous, so they may be more likely to respond. |
| 14:32 |
rfrasur |
Dyrcona++ |
| 14:33 |
rfrasur |
kmlussier: I agree. It's also REALLY easy to ignore an email that doesn't require anything beyond reading. |
| 14:34 |
yboston |
BTW, we have reached the 30 minute mark on this meeting. So far so good |
| 14:34 |
rfrasur |
I do think there can be an element of instruction included in the survey, but we also do want to know why people haven't joined. |
| 14:34 |
phasefx |
just a pointer/reminder on the help feature GHamelin is talking about: http://evergreen-ils.org/dokuwiki/doku.php?id=scratchpad:custom_help |
| 14:35 |
yboston |
I have some good ideas of why not, and I want to try to address some of them. of course I want to hear more ideas from people that are on the outside still |
| 14:35 |
yboston |
One reason I believe is keeping folks from helping is that there |
| 14:35 |
yboston |
are several things to overcome that seem overwhelming to beginners |
| 14:35 |
yboston |
like using IRC |
| 14:36 |
yboston |
like not seeing a vert simple an obvious list of "bite size" things to work on |
| 14:36 |
GHamelin |
agreed |
| 14:36 |
rfrasur |
yes...unless they may or may not have played Quake a long time ago. |
| 14:36 |
rfrasur |
definitely with regard to the "bite size" things |
| 14:36 |
GHamelin |
so once our files are complete, how do I submit to the community? |
| 14:37 |
yboston |
I keep trying to steal ideas of how we try to recruit and train potential Google Summer of Code participants |
| 14:37 |
yboston |
we being the EG developers |
| 14:37 |
* rfrasur |
has ideas...but as usual...they're not practical or ethical |
| 14:38 |
kmlussier |
GHamelin: When I started, I submitted by e-mailing docs to the DIG list. |
| 14:38 |
yboston |
Fr example, I would be open to have a google hangout meeting or even conference call with a few folks to explain our procedures |
| 14:38 |
GHamelin |
OK |
| 14:38 |
kmlussier |
After I learned AsciiDoc, I started contributing through git. But I wouldn't expect all documenters to submit their documentation with git. |
| 14:39 |
GHamelin |
training for AsciiDoc? |
| 14:39 |
kmlussier |
yboston: I think the conference call idea is a good one. Just small interactions to go through the process would be helpful. |
| 14:39 |
gsams |
of note, there is one person who was formally with NTLC who is frightened of participating in IRC |
| 14:39 |
rfrasur |
(yay for good ideas!) |
| 14:39 |
gsams |
just though I'd offer up that to yboston as extra proof |
| 14:39 |
yboston |
gsams: thanks! |
| 14:40 |
rfrasur |
frightened...how so? like overwhelmed by a diff interface? or privacy? or... |
| 14:40 |
gsams |
formerly* not formally |
| 14:40 |
gsams |
of embarrassing herself I think it was |
| 14:40 |
gsams |
I honestly had the same problem just less so |
| 14:40 |
rfrasur |
yeah, I think that's not unusual. |
| 14:40 |
gsams |
I was willing to ditch it, she really isn't so much |
| 14:41 |
kmlussier |
I don't think people need to necessarily participate in meetings either to be a DIG contributor. If it's clear what needs work and they have document to contribute, they could send it to the list without the meeting participation. |
| 14:41 |
yboston |
Perhaps we should make a video tutorial on how to try IRC or combine a conference call with participants joining in with IRC |
| 14:41 |
yboston |
we being the EG community i general (and me) |
| 14:41 |
GHamelin |
yboston: good idea! |
| 14:41 |
rfrasur |
yboston: I think that documenting about how to participate in the community is as important as documenting the software |
| 14:41 |
gsams |
rfrasur++ |
| 14:41 |
kmlussier |
As with anything, it can be difficult to interact with a new community, and if you aren't comfortable with the medium, it's an additional barrier. |
| 14:42 |
rfrasur |
especially since the software is dependent on the community |
| 14:42 |
rfrasur |
kmlussier++ |
| 14:42 |
|
stevenyvr2 joined #evergreen |
| 14:42 |
gsams |
I would also say that the more lines of communication the better(with the caveat that it's also more easily confusing) |
| 14:42 |
kmlussier |
I created an IRC quick start guide a while back that might also be useful for people. http://evergreen-ils.org/dokuwiki/doku.php?id=community:irc-quick-start&s[]=irc&s[]=quick&s[]=start |
| 14:42 |
gsams |
kmlussier++ |
| 14:43 |
yboston |
kmlussier: that page makes a huge difference |
| 14:44 |
dagreen |
And maybe it's a workload issue, too. If it's true that any little bit helps, maybe show examples of just how little a bit is. Potential members may think they aren't helping unless they contribute a huge section. |
| 14:44 |
GHamelin |
i for one will be reading this soon as i am green also |
| 14:44 |
yboston |
but I think people are afraid to interrupts. Thinking out loud I would consider creating a half hour meeting on IRC just for beginners to join in and practice in a live scenario. or maybe just during the conference or hackfst |
| 14:45 |
rfrasur |
yboston++ |
| 14:45 |
kmlussier |
yboston: I think this discussion feeds into your e-mail about using Launchpad to track documentation. We need a good way to track which documentation is needed, and bitesize tags might be good for new people just getting started. |
| 14:45 |
gsams |
yboston: Those are all excellent ideas in my opinion. |
| 14:45 |
kmlussier |
I'm not sure if LP is the right place to do it, but I think it's better than maintaining spreadsheets or wiki pages as we have in the past. |
| 14:45 |
rfrasur |
I actually kinda like the idea of using LP... |
| 14:46 |
rfrasur |
I know it's buggy and has it's own scare factor...but those are surmountable (sorry...sometimes you can't escape the big words) |
| 14:46 |
rfrasur |
hmm, s/it's/its |
| 14:46 |
yboston |
BTW, we are past the 45 minute mark |
| 14:47 |
kmlussier |
yboston: But it's a great discussion! :) |
| 14:47 |
rfrasur |
agreed :D |
| 14:47 |
yboston |
absolutely, I just want to keep everyone aware of the time, in case they want to say something |
| 14:47 |
gsams |
kmlussier: it really is, it pulled me away from trying to figure out how to install evergreen |
| 14:48 |
yboston |
that is another online class I want to teach :) |
| 14:48 |
* rfrasur |
envisions many video tutorials |
| 14:48 |
gsams |
I'd love to be a guinea pig for learning sysadmin related stuff |
| 14:49 |
yboston |
one mentality I want to adopt to try to make it easier for new comers to contribute |
| 14:49 |
yboston |
is that of a trainer |
| 14:49 |
rfrasur |
guinea_pigs++ |
| 14:49 |
yboston |
usually a trainer is not an expert on what they are teaching |
| 14:49 |
rfrasur |
yboston: I think that's a very healthy way to approach it. |
| 14:49 |
yboston |
but they have completely polished their training assignment to use every bit of the key concepts |
| 14:50 |
kmlussier |
I'm envisioning a "How to Contribute to DIG" page that links to video tutorials on AsciiDOC and also does some nice links to LP bugs with a documentation tag. |
| 14:50 |
yboston |
and avoiding examples that are confusing, and providing sample data that works really well with the training tasks |
| 14:50 |
|
mrpeters joined #evergreen |
| 14:50 |
yboston |
kmlussier: yes |
| 14:51 |
yboston |
ON a side note, I think I want to suggest that we have a DIG "Open House" |
| 14:51 |
rfrasur |
meaning? |
| 14:51 |
yboston |
we need to clean up our "lobby" a bit (the contribute page) |
| 14:52 |
yboston |
and host a meeting in IRC or google hangout or skype |
| 14:52 |
yboston |
to get to talk to folks and answer questions and lead some training |
| 14:52 |
yboston |
(just thinking out loud) |
| 14:52 |
kmlussier |
yboston: All of your ideas are great. I say we should follow through with them all. |
| 14:52 |
kmlussier |
yboston++ |
| 14:53 |
rfrasur |
yboston++ # just do everything! |
| 14:53 |
gsams |
yboston++ what they said |
| 14:53 |
yboston |
I never thought of that :) |
| 14:53 |
rfrasur |
With regard to the contribute page...is there news on the new website rollout? |
| 14:54 |
* rfrasur |
didn't go to the last meeting |
| 14:54 |
rfrasur |
bshum? |
| 14:55 |
bshum |
rfrasur: Right, so the new website. I was originally thinking to put it up last night, but then I didn't want to disrupt the DIG meeting today. |
| 14:55 |
kmlussier |
bshum++ |
| 14:56 |
bshum |
My plan was to poke it a bit more tonight. |
| 14:56 |
rfrasur |
bshum++ # ask and ye shall receive and all that |
| 14:56 |
bshum |
One thing that's going to happen for awhile is that we'll be "in transition" for a bit. But I'll be trying to pick out more prominent ways of getting people around. Like quick marking a link to the wiki, docs, etc. |
| 14:56 |
bshum |
It'll be an ongoing process. |
| 14:57 |
dbs |
rfrasur: sorry, I fell back on the paradigm of _every other piece of software in existence_ that uses F1 for help :) |
| 14:57 |
rfrasur |
of course |
| 14:57 |
yboston |
bshum: I am out of the loop, what do you mean "getting people around. " |
| 14:57 |
yboston |
(in the new site) |
| 14:57 |
kmlussier |
Navigation? |
| 14:57 |
rfrasur |
dbs++ #very glad it was that and not a change in function keys |
| 14:58 |
bshum |
Right, as regards to navigation. |
| 14:58 |
bshum |
With splitting apart the wiki from the rest of the website, navigation between sites will be a little different. |
| 14:59 |
yboston |
bshum: thanks |
| 14:59 |
rfrasur |
bshum: ty :-) |
| 14:59 |
yboston |
we have hit the our mark. we can wrap up or keep going a little bit longer. I would like to do a quick recap |
| 14:59 |
yboston |
either way |
| 15:01 |
|
gdunbar joined #evergreen |
| 15:01 |
rfrasur |
I'd say recap away |
| 15:01 |
GHamelin |
me too |
| 15:02 |
yboston |
#idea Peopel are interested in a survey, we can brainstorm on the list |
| 15:02 |
yboston |
#idea We think we should clean up the DIG welcoming page and contributing page |
| 15:02 |
yboston |
#idea We like to try online training for DIG procedures and Asciidoc. |
| 15:02 |
|
stevenyvr2 joined #evergreen |
| 15:03 |
yboston |
#idea (separate from DIG) I would like to offer experimentation time for beginners on the IRC channel |
| 15:03 |
yboston |
thoughts? |
| 15:04 |
rfrasur |
Are you refering to the Documentation list to brainstorm for the survey? |
| 15:04 |
kmlussier |
Can I add an idea about using Launchpad for tracking doc needs or was there not a consensus on that? |
| 15:04 |
rfrasur |
+1 for LP use |
| 15:05 |
kmlussier |
#idea We think Launchpad may be a better way for tracking doc needs that new volunteers can begin work on. |
| 15:05 |
yboston |
rfrasur: yes I meant the DIG list |
| 15:05 |
* kmlussier |
also plans to respond to yboston's e-mail on that topic. |
| 15:05 |
GHamelin |
+1 for all the ideas |
| 15:06 |
kmlussier |
yboston: There are a lot of ideas here. Should some of us take some specific ideas to work on so that you aren't doing it all yourself? |
| 15:06 |
yboston |
kmlussier: sure |
| 15:06 |
* kmlussier |
can work on DIG welcoming and contribution page if nobody else wants it. |
| 15:06 |
* rfrasur |
will begin working up ideas for the survey |
| 15:07 |
kmlussier |
So that I can wear my webteam and DIG hat at the same time. :) |
| 15:07 |
yboston |
kmlussier: about your ideas for launchpad, did you want to say smelting now or reply to my original email? |
| 15:07 |
rfrasur |
kmlussier: I'd be willing to work with you on that. If you'd give direction...or need help. |
| 15:07 |
rfrasur |
on the welcome/contribution page, that is |
| 15:08 |
kmlussier |
yboston: I was just thinking of supporting its use as the primary way to track our doc needs. |
| 15:08 |
yboston |
kmlussier: I see |
| 15:09 |
yboston |
#action kmlussier can work on DIG welcoming and contribution page if nobody else wants it. |
| 15:09 |
yboston |
#action rfrasur will begin working up ideas for the survey |
| 15:10 |
yboston |
#action Ybsoton will work on preparing online DIG training: DIG procedures and AsciiDoc |
| 15:11 |
yboston |
#action yboston as part of DIG and the EOB will try to promote some IRC training and experimentation opportunities for the community |
| 15:11 |
yboston |
any other comments or questions? |
| 15:11 |
rfrasur |
when we get there...(I know we actually past it already), I was wondering if there'd been a decision about a doc sprint this year...and if so, if there was a topic? |
| 15:13 |
yboston |
rfrasur: my understanding is that collectively DIG members want a doc sprint this year, though we don't always have a topic |
| 15:14 |
yboston |
I was planning on wrapping up the meeting soon, just because we are past an hour and that is what we were planning to do, but I can keep going |
| 15:14 |
rfrasur |
no, that's okay. I was just curious where it was at. |
| 15:14 |
rfrasur |
we can save it for next time. |
| 15:14 |
yboston |
I also sent out an email to the DIG list about the doc sprint but got no replies so far |
| 15:14 |
kmlussier |
I think we can wrap up. My agenda topic is getting discussion on this list, so it can continue there. |
| 15:15 |
yboston |
ok folks, this was great |
| 15:15 |
kmlussier |
yboston: I don't remember seeing that e-mail. |
| 15:15 |
rfrasur |
yboston++ |
| 15:15 |
* rfrasur |
only just subscribed to the doc list today |
| 15:15 |
yboston |
kmlussier: that is concerning. i definitely wrote something, maybe I forgot to hit send |
| 15:15 |
rfrasur |
a resend? |
| 15:15 |
yboston |
I will resend |
| 15:15 |
kmlussier |
Looking in the archives now just to be sure. |
| 15:16 |
kmlussier |
It's there. I just missed it. :) |
| 15:17 |
kmlussier |
http://markmail.org/message/qrcxvwm5gaapfg2y |
| 15:17 |
yboston |
I can resend it just the same, or just reply to it to get it going again? |
| 15:17 |
yboston |
#endmeeting |
| 15:17 |
pinesol_green |
Meeting ended Thu Aug 1 15:17:31 2013 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:17 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-08-01-14.00.html |
| 15:17 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-08-01-14.00.txt |
| 15:17 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-08-01-14.00.log.html |
| 15:17 |
kmlussier |
yboston++ #Great meeting! |
| 15:19 |
|
krvmga joined #evergreen |
| 15:19 |
krvmga |
is there a limit on the number of items that can be returned in an OPAC search? |
| 15:20 |
Dyrcona |
grabbing 0813 |
| 15:21 |
bshum |
krvmga: Sure, depending on the version of Evergreen, that's been controlled by options in opensrf.xml config. |
| 15:21 |
krvmga |
bshum: thanks. i'll take a look at ours (2.3) |
| 15:21 |
bshum |
It's just a rough estimate. Basically results per page or superpage or something |
| 15:21 |
bshum |
And number of said pages |
| 15:22 |
bshum |
I think I bumped ours to roughly 20k total hits. So it's just an estimate. |
| 15:22 |
bshum |
20 superpages, and 1000 hits each group. Something like that. |
| 15:23 |
bshum |
I don't think most patrons are going to really click through all that meaningfully. |
| 15:23 |
bshum |
But that's just my opinion. |
| 15:23 |
krvmga |
bshum: nah, you're right. i'm sure this is why google limits the number of pages that it's willing to display. and youtube does the same. |
| 15:26 |
krvmga |
bshum: yeah, we have 10 superpages, size 1000 |
| 15:27 |
rfrasur |
kmlussier: Can you give me a rough..ish idea of what it'd take to get LP set up to use for the documentation? |
| 15:27 |
bshum |
krvmga: So yep, that'll set a general limitation of 10k hits, even if there might be more. |
| 15:27 |
kmlussier |
I was just thinking we would start submitting bugs with a documentation tag. There are already some in there. |
| 15:27 |
rfrasur |
okay |
| 15:27 |
bshum |
krvmga: I bumped ours up slightly, but ultimately didn't want to get crazy since it doesn't matter much more at that scale. |
| 15:28 |
krvmga |
bshum: i think youtube limits to 1000 and google to 3000 |
| 15:28 |
* kmlussier |
re-reads yboston's e-mail to see if that is what he had in mind. |
| 15:28 |
bshum |
Plus in the very early days of TPAC, things were slower and having more superpages added to the slowness (kinda) |
| 15:29 |
bshum |
Well, at least you know where to experiment now. |
| 15:29 |
krvmga |
lol. 'cause that's why i like to do...poke evergreen with a stick and see what happens |
| 15:30 |
krvmga |
it usually just works out so well. |
| 15:30 |
pinesol_green |
[evergreen|Ben Shum] LP1204273 - Repair org unit settings for making state not required - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d2ef168> |
| 15:30 |
pinesol_green |
[evergreen|Jason Stephenson] Stamping upgrade script for LP1204273. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=72e2f93> |
| 15:34 |
|
Shae joined #evergreen |
| 15:56 |
rfrasur |
(ooo...I gave my first "this is not a gym" speech of the school year) |
| 16:03 |
|
zerick joined #evergreen |
| 16:20 |
moodaepo |
@marc 800 |
| 16:20 |
pinesol_green |
moodaepo: An author/title series added entry in which the author portion is a personal name. (Repeatable) [a,b,c,d,e,f,g,h,j,k,l,m,n,o,p,q,r,s,t,u,v,4,6,8] |
| 16:20 |
moodaepo |
@marc 830 |
| 16:20 |
pinesol_green |
moodaepo: A series added entry consisting of a series title alone. (Repeatable) [a,d,f,g,h,k,l,m,n,o,p,r,s,t,v,6,8] |
| 16:21 |
moodaepo |
@marc 490 |
| 16:21 |
pinesol_green |
moodaepo: A series statement for which no series added entry is traced or for which the added entry is traced in one of the 800-830 fields in a form different from the form contained in field 490. (Repeatable) [a,l,v,x,6,8] |
| 16:26 |
|
acoomes joined #evergreen |
| 16:56 |
|
gsams_ joined #evergreen |
| 17:03 |
Dyrcona |
logs? |
| 17:03 |
Dyrcona |
We don't have that as a factoid, eh? |
| 17:07 |
senator |
~logs |
| 17:08 |
pinesol_green |
logs is You can find the logs for this channel at http://evergreen-ils.org/irc_logs/ |
| 17:08 |
senator |
our factoids have lame syntax :-( |
| 17:08 |
Dyrcona |
Oh. I did it wrong... |
| 17:08 |
senator |
(not to slight csharp or bshum or anyone else making that work in the first place) |
| 17:08 |
Dyrcona |
right. |
| 17:08 |
Dyrcona |
It thought it worked the same as in #koha. |
| 17:08 |
bshum |
Mostly csharp. |
| 17:09 |
bshum |
I don't toy with it much. |
| 17:09 |
bshum |
Though we should update that factoid soon. |
| 17:09 |
bshum |
irc.evergreen-ils.org is where new logs live. |
| 17:09 |
bshum |
Though I'm still finding time to migrate all our old logs over to it. |
| 17:10 |
|
mmorgan left #evergreen |
| 17:16 |
|
stevenyvr2 joined #evergreen |
| 17:28 |
bshum |
Maybe it's just me |
| 17:44 |
|
acoomes joined #evergreen |
| 18:06 |
|
dboyle joined #evergreen |
| 18:12 |
|
stevenyvr2 joined #evergreen |
| 21:12 |
|
rsinger joined #evergreen |
| 21:37 |
|
zxiiro joined #evergreen |
| 22:48 |
|
stevenyvr2 joined #evergreen |
| 22:49 |
|
stevenyvr2 left #evergreen |
