| Time |
Nick |
Message |
| 00:53 |
|
dcook joined #evergreen |
| 02:12 |
|
b_bonner joined #evergreen |
| 02:14 |
|
mnsri_away joined #evergreen |
| 04:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 07:11 |
|
rjackson_isl joined #evergreen |
| 07:47 |
|
Callender joined #evergreen |
| 08:09 |
|
agoben joined #evergreen |
| 08:26 |
|
_adb joined #evergreen |
| 08:41 |
|
kmlussier joined #evergreen |
| 08:43 |
|
mmorgan joined #evergreen |
| 08:49 |
|
bos20k joined #evergreen |
| 08:53 |
|
collum joined #evergreen |
| 09:04 |
|
Dyrcona joined #evergreen |
| 09:18 |
|
yboston joined #evergreen |
| 09:20 |
|
alynn26 joined #evergreen |
| 09:28 |
Dyrcona |
I just noticed that the default crontab still runs the old hold targeter. |
| 09:28 |
Dyrcona |
Should we switch to hold_target_v2? |
| 09:28 |
Dyrcona |
bah... |
| 09:29 |
kmlussier |
Yeah, we probably should. |
| 09:30 |
gmcharlt |
jeffdavis: I call your attention to bug 1552861, where you may want to double-check how I'm proposing we deal with invalid values during upgrade |
| 09:31 |
pinesol_green |
Launchpad bug 1552861 in Evergreen 2.11 "Incorrect datatype for Default Record Match Set org setting" [Low,Confirmed] https://launchpad.net/bugs/1552861 |
| 09:33 |
gmcharlt |
Dyrcona: kmlussier: then it sounds like thorough testing of bug 1677661 would be right up your alley prior to changing the stock crontab :) |
| 09:33 |
pinesol_green |
Launchpad bug 1677661 in Evergreen "Hold Targeter V2 Repairs & Improvements" [Undecided,New] https://launchpad.net/bugs/1677661 |
| 09:33 |
gmcharlt |
shameless RM is shameless ;) |
| 09:35 |
Dyrcona |
gmcharlt: I will gladly test it. I am in the middle of writing an email saying I want to test it before I enable it on the training server to local staff. :) |
| 09:35 |
gmcharlt |
:) |
| 09:35 |
kmlussier |
Dyrcona++ |
| 09:41 |
|
bos20k joined #evergreen |
| 09:48 |
|
DianeD joined #evergreen |
| 10:15 |
|
alynn26 joined #evergreen |
| 10:24 |
|
terran_ joined #evergreen |
| 10:36 |
|
collum_ joined #evergreen |
| 10:36 |
gmcharlt |
Dyrcona: by the way, https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1602 is a 404 for me (re an update you made to https://wiki.evergreen-ils.org/doku.php?id=dev:2017_new_tools) |
| 10:37 |
Dyrcona |
Odd. Today it is asking me to sign in. |
| 10:39 |
Dyrcona |
Try this one: https://gitlab.com/gitlab-org/gitlab-ce/issues/22095 |
| 10:39 |
Dyrcona |
I'll update the wiki. |
| 10:41 |
gmcharlt |
Dyrcona: thanks, that one works for me |
| 10:41 |
Dyrcona |
The other one was linked to from that second one. |
| 10:41 |
Dyrcona |
It worked for me the other day. |
| 10:53 |
Dyrcona |
It works for me if I click the link from the 22095 issue. |
| 11:12 |
* jeff |
added comments to that bullet point |
| 11:19 |
JBoyer |
Huh. Dancer hates warnings even more than I do: request to POST / crashed: Warning caught during route execution: Use of uninitialized value in scalar assignment at /usr/.../oilsMessage.pm line 246. in /usr/.../Dancer/Handler.pm |
| 11:20 |
JBoyer |
($ENV{TZ} is unset) |
| 11:22 |
|
mmorgan1 joined #evergreen |
| 11:23 |
|
mmorgan2 joined #evergreen |
| 11:23 |
|
mllewellyn joined #evergreen |
| 11:25 |
|
mmorgan3 joined #evergreen |
| 11:35 |
|
Christineb joined #evergreen |
| 11:36 |
Dyrcona |
Grr. None of the services that talk to the db will star on my vm. |
| 11:37 |
Dyrcona |
I just ran eg_db_config with the correct parameters, too. |
| 11:37 |
Dyrcona |
I can connect with psql using the same parameters. |
| 11:37 |
Dyrcona |
Anyone seen that before? |
| 11:38 |
Dyrcona |
Oh. it might be may memcached settings. |
| 11:38 |
Dyrcona |
This is what happens when you copy a config from production.... |
| 11:39 |
JBoyer |
Dyrcona: problem found re:NCIPServer, I can't convince Dancer that an uninitialized value warning isn't a hill worth dying on. :/ (the values of environments/*.yml don't matter) |
| 11:42 |
Dyrcona |
JBoyer: Yeah. I see your message from earlier. I was in a meeting. Looks like it has to do with the new timezone code in 2.12. |
| 11:43 |
Dyrcona |
Have you tried setting it in your Apache config as a PerlEnvVar or whatever? |
| 11:43 |
JBoyer |
I was scrolled up a bit and didn't see that you'd been back and was pinging you for whenever. |
| 11:44 |
JBoyer |
I've tried a couple things, env vars don't seem to make it through to the app. |
| 11:44 |
JBoyer |
(There's a comment to that effect in the code, but no clues.) |
| 11:44 |
JBoyer |
I'm trying a couple other things right now. |
| 11:46 |
|
alynn26 joined #evergreen |
| 11:47 |
JBoyer |
Oh, there's nothing we can do in Apache to define $ENV{TZ} because that error is coming from deep inside OpenSRF. The best we can hope for is telling it to stop dying on warnings, which I'm still not having any luck with. |
| 11:48 |
Dyrcona |
Heh. I lost my network connectivity a couple of times while in the meeting, but my client acts like it never disconnected. |
| 11:48 |
JBoyer |
(nothing to do meaning I think it's in an entirely different process at that point) |
| 11:48 |
Dyrcona |
Ah. I see. |
| 11:48 |
Dyrcona |
Well, the vm I'm fiddling with right now is one where I plan to test this, so I should be able to start looking later today or tomorrow. |
| 11:49 |
Dyrcona |
I just got my configuration issues squared away and all services are running. |
| 11:50 |
JBoyer |
I'm perusing the Dancer docs since this shuts down our resource sharing system for over half of its users, so I'm not planning to work on anything else today so it's no rush if you've got things vying for your time today. |
| 11:50 |
JBoyer |
My grammar module has obviously crashed also. |
| 11:50 |
Dyrcona |
:) |
| 11:51 |
Dyrcona |
I'm can't seem to purge my typo package. |
| 11:52 |
Dyrcona |
Me spill chucker woks grate. I needle gamma chicken. :) |
| 11:55 |
|
remingtron joined #evergreen |
| 12:01 |
|
jihpringle joined #evergreen |
| 12:26 |
|
plux joined #evergreen |
| 12:28 |
mmorgan |
I have an action trigger running nightly that marks circulations Long Overdue. |
| 12:28 |
mmorgan |
I also have a group penalty threshold that applies PATRON_EXCEEDS_LONGOVERDUE_COUNT to all users for the consortium with the threshold set at 1 |
| 12:29 |
mmorgan |
I can see that the penalty gets applied when the patron is retrieved at a circ desk, but it doesn't appear to be applied as a result of the long overdue trigger. |
| 12:29 |
mmorgan |
How else are penalties applied? Should a process be run regularly to apply penalties? |
| 12:34 |
Dyrcona |
Mostly penalties are applied either by the fine generator or at checkin. |
| 12:40 |
mmorgan |
Does the fine generator calculate penalties only for transactions/users for which it assessed a fine? |
| 12:41 |
Dyrcona |
I believe it is part of the fine code, so it happens at checkin, too. I could double check if you like. |
| 12:43 |
mmorgan |
Dyrcona: Can you point me to the fine code and I'll take a look? I'm not sure where that lives. |
| 12:44 |
Dyrcona |
Yes, just a minute. |
| 12:44 |
Dyrcona |
If you're asking specifically about long overdue, there's an a/t for that. |
| 12:44 |
|
DianeD joined #evergreen |
| 12:45 |
mmorgan |
Yes, specifically long overdue. |
| 12:47 |
Dyrcona |
Ah. That should be an action trigger. |
| 12:48 |
mmorgan |
The Lost/Long overdue seems to happen in AssetCommon.pm |
| 12:49 |
mmorgan |
and it looks like penalties should be calculated there. |
| 12:49 |
Dyrcona |
That code may do it if you manually set it. |
| 12:49 |
JBoyer |
FANTASTIC. I've been changing one server and testing another. It's working, but now I have no idea why. |
| 12:49 |
mmorgan |
Ah. ok. |
| 12:49 |
Dyrcona |
The default name of the trigger is 90 Day Overdue Mark Lost. |
| 12:50 |
bshum |
JBoyer: The chaos monkey strikes again! |
| 12:52 |
mmorgan |
The default Long Overdue trigger is 6 Month Overdue Mark Long-Overdue |
| 12:52 |
kmlussier |
JBoyer: I can't tell you how many times I've done the same. |
| 12:52 |
Dyrcona |
mmorgan: The trigger should eventually end up in the code that you're looking at in AssetCommon.pm: set_item_lost_or_lod |
| 12:52 |
mmorgan |
Ok, thanks for confirming that. |
| 12:53 |
Dyrcona |
mmorgan: They'll do either depending on settings, IIRC, but I don't mess with triggers that much. |
| 12:53 |
mmorgan |
I will poke around a bit more. Don't want to take up more of your time. Thanks!! |
| 12:53 |
mmorgan |
Dyrcona++ |
| 12:53 |
kmlussier |
gmcharlt: I see that we have a web client feedback fest next week. Is that going to be similar to Bug Squashing week in that those who are participating will do so as time allows? |
| 12:54 |
Dyrcona |
mmorgan: generate_fines in CircCommon.pm also calculates penalties. |
| 12:54 |
gmcharlt |
kmlussier: I will be sending more details this afternoon or tomorrow |
| 12:54 |
mmorgan |
Ok, thanks! |
| 12:54 |
Dyrcona |
Checkin should end up in there at some point, too. |
| 12:55 |
kmlussier |
gmcharlt: Great, thanks! |
| 12:55 |
Dyrcona |
and the fine generator. |
| 12:55 |
gmcharlt |
but it's not just web client, it's all pull requests, and I'm not proposing that folks would need to tightly schedule their time |
| 12:55 |
kmlussier |
gmcharlt: Gotcha. I guess that means I can't use it as an excuse to get out of a meeting. ;) |
| 12:56 |
gmcharlt |
kmlussier: correction - everybody will be required to spend all time from 9-5 to participate! ;) |
| 12:58 |
Dyrcona |
:) |
| 13:15 |
* mmorgan |
has confirmed that penalties are indeed calculated after the nightly mark long overdue action trigger is run. |
| 13:16 |
mmorgan |
I was using the test mode for the trigger definition, which apparently does not calculate the penalties. |
| 13:25 |
|
ohiojoe joined #evergreen |
| 13:29 |
Dyrcona |
mmorgan++ |
| 13:41 |
kmlussier |
Heads up. Evergreen web team meeting in 19 minutes. |
| 13:47 |
|
ericar joined #evergreen |
| 13:58 |
|
jlundgren joined #evergreen |
| 13:58 |
|
alynn26 joined #evergreen |
| 13:59 |
kmlussier |
Web team meeting is beginning in a minute |
| 14:00 |
JBoyer |
Dyrcona: To use NCIPServer on OpenSRF 2.5+ you need to include SetEnv DANCER_ENVIRONMENT "production" inside the <Location /NCIP/> stanza. |
| 14:00 |
alynn26 |
P |
| 14:01 |
kmlussier |
#startmeeting 2017-05019 - Evergreen Web Team Meeting |
| 14:01 |
pinesol_green |
Meeting started Wed May 10 14:01:27 2017 US/Eastern. The chair is kmlussier. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:01 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 14:01 |
pinesol_green |
The meeting name has been set to '2017_05019___evergreen_web_team_meeting' |
| 14:01 |
kmlussier |
Oops. Looks like I messed up the date. :( |
| 14:01 |
kmlussier |
#info Agenda is available at https://wiki.evergreen-ils.org/doku.php?id=webteam:meetings:agenda:2017-05-10 |
| 14:02 |
kmlussier |
#topic Introductions |
| 14:02 |
kmlussier |
Please introduce yourselves as follows: |
| 14:02 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 14:02 |
jlundgren |
#info jlundgren is Jeanette Lundgren, C/W MARS |
| 14:03 |
|
ggrae joined #evergreen |
| 14:03 |
graced |
#info graced is Grace Dunbar, Equinox Open Library Initiative |
| 14:03 |
collum_ |
#info collum is Garry Collum, Kenton County Public Library |
| 14:03 |
DianeD |
DianeD is Diane Disbro, Missouri Evergreen |
| 14:03 |
sallyf |
#info is Sally Fortin, Equinox Open Library Initiative |
| 14:03 |
alynn26 |
#info alynn26 is Lynn Floyd, Anderson County Library |
| 14:03 |
ericar |
#info ericar is Erica Rohlfs, Equinox Open Library Initiative |
| 14:04 |
terran_ |
#info terran_ is Terran McCanna, PINES |
| 14:04 |
ggrae |
#info ggrae is Angela Simmons-Jones, Houston County Public Library System in Georgia |
| 14:04 |
ohiojoe |
#info ohiojoe is Joe Knueven, Germantown PL, Consortium of Ohio Libraries |
| 14:04 |
abneiman |
#info abneiman is Andrea Buntz Neiman, Equinox |
| 14:05 |
kmlussier |
Great, it's good to see new names in here! |
| 14:05 |
|
rhamby joined #evergreen |
| 14:05 |
rhamby |
sorry about that quassel decided to die on me suddenly |
| 14:05 |
kmlussier |
People who wander in late can introduce themselves as they arrive. |
| 14:05 |
kmlussier |
rhamby: Likely story. ;) |
| 14:06 |
rhamby |
#info rhamby = Rogan Hamby, Equinox |
| 14:06 |
gmcharlt |
#info gmcharlt is Galen Charlton, EOLI |
| 14:06 |
rhamby |
kmlussier: I never avoid meetings you're running, that's how I end up volunteered for extra things |
| 14:06 |
kmlussier |
rhamby: Darn! You weren't supposed to figure that out? |
| 14:06 |
kmlussier |
Before we start, I would like to give some background for those who are new to a web team meeting... |
| 14:07 |
kmlussier |
The web team is responsible for the ongoing care and feeding of the Evergreen web site, for keeping content up to date, and for ensuring that the content meets the needs of the Evergreen community. |
| 14:07 |
kmlussier |
The team hasn't met in about two years, and web site contributors have been updating content and addressing technical issues. |
| 14:07 |
kmlussier |
By meeting regularly again, I'm hoping we can re-focus on adding new content to the site, if needed, keeping the blog up to date, and possibly thinking of the site design. |
| 14:07 |
kmlussier |
If you're new to the web team meeting and found out about it via the general list, I recommend you sign up for the web team list. |
| 14:08 |
kmlussier |
#link http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team |
| 14:08 |
kmlussier |
We have a good turnout today, so welcome! I'm glad you all could join us! |
| 14:08 |
kmlussier |
We do have some very old action items remaining from a meeting that I'm going to run through now, but I think we can dispense with all but a couple of them so that we can all start fresh. |
| 14:09 |
kmlussier |
#topic Action Items from Previous Meetings |
| 14:09 |
kmlussier |
#info gmcharlt has put an Evergreen logo and link back to the main web site on irc.evergreen-ils.org |
| 14:09 |
kmlussier |
As a note of explanation, several years ago, the Evergreen Oversight Board requested that all pages that fall within the evergreen-ils.org domain contain an Evergreen logo with a link to the main site. |
| 14:09 |
kmlussier |
gmcharlt++ |
| 14:09 |
kmlussier |
#info kmlussier has contacted all but one of the people who has a WordPress account to ask if they give consent to license the content under CC BY-SA. 24 of the 37 people with accounts have consented. |
| 14:10 |
kmlussier |
If anyone knows any of the remaining folks on the list, I would appreciate help in reaching out. |
| 14:10 |
kmlussier |
The list is available at https://docs.google.com/spreadsheets/d/1dJvPa2OxwSO7m_-8WN0qGJ7bYBM-VPyYAmB4jNg2Dd8/edit?usp=sharing. |
| 14:10 |
kmlussier |
I do have on follow-up question from this action item. |
| 14:11 |
kmlussier |
Some of the account-holders are listed as having 0 posts on the site. This could mean one of two things: |
| 14:11 |
kmlussier |
They may have contributed to the site by creating/editing WordPress pages, which isn't reflected in this number. |
| 14:11 |
kmlussier |
Or they may have never contributed any content, meaning that the consent isn't really needed in the end. |
| 14:11 |
kmlussier |
I'm wondering how important it is to get consent from those users if we ultimately aren't able to reach them. |
| 14:12 |
rhamby |
kmlussier: worst case scenario we can put language on those pages that the content is exempt from the wider CC license but I would either do that or remove it, not automatically consider it in the license |
| 14:13 |
dbs |
It's a risk calculation. How likely is it for one of those users to take legal action or be upset if we make their content available. |
| 14:13 |
dbs |
I would say the likelihood is low. And if we can flag pages where they've contributed, we could mark them as such? |
| 14:14 |
|
mmorgan left #evergreen |
| 14:14 |
abneiman |
not sure of the legalities, but we want to make sure we carefully document that there was a good-faith effort to contact them -- "X webteam member contacted Y content owner at Z email address on Date", etc. |
| 14:14 |
graced |
Also, based off who is left on the list I think we can come close to tracking everyone down. |
| 14:14 |
dbs |
#info dbs is Dan Scott, Laurentian |
| 14:14 |
rhamby |
dbs: I think we're having the same thought from different angles, risk is low but we can't include their content under the CC w/o their assignment of it IMO |
| 14:14 |
kmlussier |
Yeah, so it's easy for me to see which blog posts those authors contributed to. But, through the admin interface, I can't really see what pages they may have edited. |
| 14:14 |
kmlussier |
Can somebody else find that information through the database? |
| 14:14 |
dbs |
abneiman++ # yep |
| 14:14 |
rhamby |
kmlussier: at least in the US their just editing leaves it still as a derivative work and they have no say in it's copyright status |
| 14:14 |
kmlussier |
graced: Yes, I agree most we should be able to track down. |
| 14:15 |
kmlussier |
graced: But there is still one person I haven't been able to find contact information for. |
| 14:16 |
kmlussier |
OK, well my hope is to get a response from most, if not all, the people. If there are any left, we can revisit. Thanks for the feedback! |
| 14:16 |
kmlussier |
So the next outstanding action item I'm going to turn into a new action item assigned to me. |
| 14:16 |
kmlussier |
#action kmlussier to send notification of license clarification to the mailing list after getting more responses from current authors on the CC BY-SA licensing. |
| 14:17 |
kmlussier |
And then we have a few other action items that are either done or no longer relevant. |
| 14:17 |
kmlussier |
#info RoganH (aka rhamby) did indeed get the 2016 conference folks set up with WordPress accounts |
| 14:17 |
kmlussier |
rhamby++ |
| 14:17 |
kmlussier |
Would somebody like to take an action item to set up the 2018 conference folks with WordPress accounts? |
| 14:17 |
rhamby |
I'll volunteer for it again |
| 14:18 |
kmlussier |
rhamby: Thanks! |
| 14:18 |
rhamby |
I'm on the conference list so easy enough to do |
| 14:18 |
kmlussier |
#action rhamby to contact 2018 conference folks to get WordPress accounts to manage the conference site. |
| 14:18 |
kmlussier |
#info webstats has been disabled on the web site, negating the need to add a robots.txt to disallow crawling. |
| 14:19 |
kmlussier |
Any questions about the old action items before I move on? |
| 14:19 |
kmlussier |
#topic Evergreen Community Tutorials |
| 14:20 |
kmlussier |
Christineb asked me to raise this question |
| 14:20 |
kmlussier |
#link https://www.youtube.com/playlist?list=PLdwlgwBNnH4riThcmOwvdLTddsn435RcJ |
| 14:20 |
kmlussier |
IG (the Documentation Interest Group) would like to add a link to the tutorials from the web site. |
| 14:20 |
kmlussier |
Sorry, that should be DIG, not IG |
| 14:21 |
kmlussier |
Christineb wanted to know if we have a preference for placing the link. |
| 14:21 |
kmlussier |
Her thoughts were either add it to the Documentation menu or add it to the wiki page at https://evergreen-ils.org/eg-documentation/ |
| 14:21 |
kmlussier |
Any thoughts on that? |
| 14:21 |
rhamby |
my gut reaction is to add it to the documentation menu |
| 14:22 |
kmlussier |
I think it will get the most visibility there. |
| 14:22 |
rhamby |
that was my thought |
| 14:22 |
DianeD |
how about create a new tab? |
| 14:22 |
DianeD |
something like "Circ Helps" |
| 14:23 |
DianeD |
I know all the videos aren't about circ but then circ people wouldn't need to search for help |
| 14:23 |
kmlussier |
DianeD: By new tab, do you mean the dropdown menus along the top? |
| 14:23 |
graced |
OOC, who curates that channel - just BC Coop? Will it be actively curated for content and kept up to date? |
| 14:24 |
DianeD |
Yes - a new option along the top |
| 14:24 |
kmlussier |
graced: That's the plan. DIG is working to keep that content up to date from what I understand. |
| 14:24 |
graced |
cool, I like plans |
| 14:25 |
rhamby |
I'd prefer the branding be a bit more Evergreen centric and it does need to be up to date (the 2.9 upgrade video can probably go) |
| 14:25 |
kmlussier |
DianeD: My only concern with the new tab is that we generally have categories listed up there with links fitting that category underneath. In this case, it's just the one link. |
| 14:25 |
rhamby |
but I really like the idea of the video series and much karma to the dig folks for it |
| 14:25 |
kmlussier |
Merchandising is currently the exception to that rule. At one time, I was thinking we might expand that section. |
| 14:26 |
rhamby |
to be fair if we progress with plans for a site overhaul some of that might get moved around |
| 14:26 |
DianeD |
we could put more stuff for circ in a circ link |
| 14:26 |
abneiman |
agreed with adding it under the doc menu; also that menu is only 4 items currently so it won't be crowded/hard to find |
| 14:26 |
rhamby |
+1 to doc menu for now (might get changed during site overhaul) |
| 14:27 |
Christineb |
I can give perms to anyone that wants the ability to update the playlist |
| 14:27 |
Christineb |
sorry just jumping in on another call |
| 14:27 |
kmlussier |
rhamby: Good point. For now, then, I think we might want to keep it within the current info architecture, but maybe we rethink the way the site is organized with an overhaul. |
| 14:27 |
collum_ |
Is there an active wordpress plugin to pull in youtube channels automatically? |
| 14:27 |
kmlussier |
collum_: Probably |
| 14:28 |
|
alynn26_ joined #evergreen |
| 14:29 |
rhamby |
Christineb: I'll gladly take an invite to the channel maintenance to help out with it |
| 14:29 |
kmlussier |
collum_: Would you like to take an action item to investigate YouTube plugins to see if there is a way to better integrate those into the site? |
| 14:29 |
collum_ |
Will do. |
| 14:29 |
kmlussier |
collum++ |
| 14:30 |
bshum |
Just circling back to an earlier topic, but this paste shows a quick query I assembled on the wordpress database to count out who has made page edits in wp_posts (aka, wordpress pages and posts): https://pastebin.com/7k0PmwSm |
| 14:30 |
bshum |
You can cross that against the users with accounts to eliminate users who have not exercised their access. |
| 14:30 |
kmlussier |
#action collum to investigate YouTube WordPress plugins to see if there is a better way to integrate the tutorials into the evergreen-ils.org site. |
| 14:30 |
kmlussier |
bshum++ |
| 14:31 |
kmlussier |
I'll take an action item to do that cross checking. |
| 14:32 |
kmlussier |
To finish up on this topic, I would say we should put the link in the documentation menu for now, explore the YouTube plugin, and keep in mind of alternate ways of organizing it if/when we overhaul the site. |
| 14:32 |
kmlussier |
Are there any objections to the above? |
| 14:33 |
graced |
+1 to the plan |
| 14:33 |
rhamby |
+1 for great justice |
| 14:33 |
kmlussier |
OK, moving on then |
| 14:33 |
|
jvwoolf joined #evergreen |
| 14:33 |
kmlussier |
#topic New and blue sky projects |
| 14:34 |
kmlussier |
#link https://docs.google.com/spreadsheets/d/1e2n3A0cVxbmbvMnRKTw4Y3Vtl5DkL4vv9eQAfw2CzvM/edit?usp=sharing |
| 14:34 |
kmlussier |
This is a spreadsheet where we were tracking tasks that we wanted to do on the web site and, in some cases, what we were actively working on. |
| 14:35 |
alynn26_ |
+1 |
| 14:35 |
kmlussier |
The In-Progress has some in-progress tasks with people assigned to them. If your name is assigned to one of these tasks, I'm asking that you update the progress if there is any to report. |
| 14:36 |
kmlussier |
Or, if you are no longer willing to work on the task, I'm asking that you remove your name and maybe set it back to New so that it's eligible for somebody else to work on. |
| 14:37 |
kmlussier |
Given that this is the first time we've met in a while and that there are new people involved, I'm guessing there are new things people want to add to the list. |
| 14:37 |
|
tspindler joined #evergreen |
| 14:39 |
kmlussier |
I'm thinking maybe we should work over the next month on updating this list. Updating progress, removing assginments when needed, and adding new projects to the New tab. |
| 14:39 |
kmlussier |
And then when we meet again in June, we could look at what's there, prioritize, and try to find some volunteers to work on some items. |
| 14:40 |
dbs |
gmcharlt: LDAP (or the like) as common auth backend for wiki & website could also serve as the backbone of dev tools replacements (LP, gitolite, etc) - I had suggested that in the context of the dev discussions, but fun to see it here too |
| 14:40 |
kmlussier |
Does that approach work for anyone? Does anyone have any burning projects they would like to make sure gets on there? |
| 14:40 |
gmcharlt |
dbs: indeed |
| 14:41 |
rhamby |
I'll do some research towards some of the blue sky issues I'm interested in and add them to in progress |
| 14:41 |
graced |
kmlussier: I think that works - do you want to put any constraints on our crazy ideas? |
| 14:41 |
ohiojoe |
+1 to the approach suggested |
| 14:42 |
kmlussier |
graced: Good question. |
| 14:42 |
kmlussier |
Given our next item on the agenda, I think we need to keep in mind that we may be doing a site overhaul. |
| 14:43 |
kmlussier |
So the constraints I have in mind are that, when working with this list, we work within the current architecture. Adding content is great, researching plugins to support that content is okay too. |
| 14:43 |
kmlussier |
But, for now, I think we should avoid moving content all over the place. |
| 14:43 |
graced |
seems reasonable |
| 14:43 |
kmlussier |
But those are my own thoughts. Does anyone else have suggestions for constraints? |
| 14:45 |
rhamby |
I'd like to put the web site overhaul a bit up front in that we need to make sure that other things (e.g. youtube plugins) work with it. |
| 14:46 |
kmlussier |
rhamby: So what you're saying is focus just on the content right now and no new plugins until an overhaul is done? |
| 14:46 |
rhamby |
kmlussier: or at least don't settle on anything like plugins until we know our course on the overhaul (i.e. have picked a theme and can know compatability) |
| 14:46 |
kmlussier |
My only concern with that is if the overhaul takes a very long time, in which case we're waiting to do new things. |
| 14:46 |
rhamby |
that doesn't preclude research but I'd hate to work on implementing something and find the work broken by the overhaul |
| 14:47 |
rhamby |
we can fast track an overhaul :) |
| 14:47 |
kmlussier |
Sure, so let's include them on the list, but maybe when we prioritize next month, we can put those a little later in the process. |
| 14:48 |
kmlussier |
To wrap up this discussion then, I'll take an action item to send an email to the webteam list asking people to add content to that spreadsheet. |
| 14:49 |
kmlussier |
#action kmlussier to send email to webteam list inviting web site tasks spreadsheet with new features they want to see on the site. |
| 14:50 |
kmlussier |
#topic New Wordpress Theme for Evergreen web site |
| 14:50 |
kmlussier |
A couple of people have commented to me that they think it is time to change the WordPress theme for the site. A new theme will provide a new look and feel for the site. |
| 14:50 |
|
Jillianne joined #evergreen |
| 14:50 |
kmlussier |
I wanted to start by putting that question out there to see if there is general consensus that we should consider changing the theme for the site. |
| 14:50 |
kmlussier |
If there is, then we can discuss volunteers for working on it. |
| 14:50 |
rhamby |
I volunteer as tribute. |
| 14:50 |
kmlussier |
What do you think? |
| 14:51 |
* rhamby |
thinks his opinion is known |
| 14:51 |
graced |
I think we need a new look/theme and I volunteer to work on it |
| 14:51 |
kmlussier |
rhamby: And I didn't even twist your arm. Or graced's. |
| 14:51 |
rhamby |
I'm in a volunteering mood today. Lord help me. |
| 14:52 |
kmlussier |
OK, we have two people who have voiced their support to this idea. They also happen to be the two people who suggested the idea to me. |
| 14:52 |
kmlussier |
What do others think? |
| 14:52 |
collum_ |
You can put me on the list, as well. |
| 14:52 |
kmlussier |
rhamby: If I had know that, I would have paused before volunteering for my previous action items. |
| 14:52 |
DianeD |
we need to ask the questions - who uses the website, what service does it provide, how to entice more people to use it |
| 14:52 |
rhamby |
kmlussier: let's not debase this rare moment |
| 14:53 |
jlundgren |
I volunteer to help as well |
| 14:53 |
kmlussier |
DianeD: Do you think we need to ask those questions before deciding whether to look into new themes. Or are you saying we need to do it as part of the process? |
| 14:54 |
ohiojoe |
I think a fresh theme isn't a bad idea. I like the idea of something to coincide with the 3.0 release (unless we try to do something more ambitious by then) |
| 14:54 |
DianeD |
part of the process |
| 14:54 |
* kmlussier |
also notes that she hasn't heard any objections yet. |
| 14:54 |
kmlussier |
DianeD: In that case, can I add you to the volunteer list as well? |
| 14:54 |
kmlussier |
Also, who is leading this project. |
| 14:54 |
* kmlussier |
hopes the answer is not the web team chair. |
| 14:55 |
DianeD |
Yes - but not in any technical aspect |
| 14:55 |
kmlussier |
Not that I object, but it's a matter of tuits. |
| 14:55 |
rhamby |
I was involved in the last discussion about the audience and all that and don't want to carry that bias over so I'd rather work with someone else leading it. |
| 14:55 |
ohiojoe |
And I'd be willing to help as well |
| 14:56 |
kmlussier |
graced: I'm also thinking the Outreach messaging discussion can play into this if we're talking about coinciding with a 3.0 release. |
| 14:56 |
rhamby |
We've had the discussion about audience before but I think it's revisiting with fresh eyes. |
| 14:56 |
graced |
I'll volunteer to head it up if no one else is keen on leading |
| 14:56 |
rhamby |
graced++ |
| 14:56 |
kmlussier |
Thank you graced. |
| 14:56 |
kmlussier |
graced++ |
| 14:56 |
jlundgren |
graced++ |
| 14:57 |
ohiojoe |
graced++ |
| 14:57 |
collum_ |
graced++ |
| 14:57 |
graced |
kmlussier: Much as I'd like, we can't make you do ALL the things |
| 14:57 |
graced |
:) |
| 14:57 |
kmlussier |
:) |
| 14:57 |
DianeD |
I can be the lowly enduser who fixes computer problems by turning the thing off and on again but wants to reach other endusers. |
| 14:57 |
kmlussier |
We do have a test server available where I think playing can happen. http://test-www.evergreen-ils.org/ |
| 14:57 |
kmlussier |
DianeD: I think it's important we have that perspective. |
| 14:58 |
kmlussier |
I think the test server needs some WordPress updates, though. |
| 14:58 |
kmlussier |
graced: Do you think it will be possible for your group to meet and report back in time for our June meeting? |
| 14:59 |
kmlussier |
Or, maybe not meet, but discusss. |
| 14:59 |
graced |
Barring vacation scheduling issues... yes I think so |
| 14:59 |
kmlussier |
Great. |
| 14:59 |
kmlussier |
#action graced to head team to investigate new web site theme. |
| 15:00 |
collum_ |
Same credentials on test server and real server? |
| 15:00 |
kmlussier |
#action rhamby DianeD ohiojoe collum jlundgren to work on team to investigate new web site theme |
| 15:00 |
kmlussier |
If I missed anyone, let me know. |
| 15:01 |
kmlussier |
collum_: I think so, but I don't know how old the user data is on that system. |
| 15:01 |
kmlussier |
gmcharlt: Would it be easy to update the test server with fresh data? |
| 15:02 |
gmcharlt |
kmlussier: sure |
| 15:02 |
kmlussier |
gmcharlt: Would you be willing to do an update on it? |
| 15:02 |
dbs |
(ignore this) We should totally rewrite the website in Angular to match our AngularJS-based 3.0 release! |
| 15:02 |
kmlussier |
dbs: Stop! |
| 15:02 |
graced |
bad dbs, no cookie |
| 15:03 |
rhamby |
dbs: I've actually been looking at angular embedded in wordpress lately .... |
| 15:03 |
collum_ |
dbs++ |
| 15:03 |
kmlussier |
OK, I'm moving on to the next topic before this idea goes too far. |
| 15:03 |
gmcharlt |
kmlussier: yep, I'll take the action itme |
| 15:03 |
kmlussier |
gmcharlt++ |
| 15:04 |
kmlussier |
#topic Meeting Schedule |
| 15:04 |
kmlussier |
Can we set the regular meeting time to the second Wednesday of the month at the same time or do folks want me to do another Doodle poll? |
| 15:04 |
graced |
I'd prefer a poll for a regular time.... |
| 15:05 |
abneiman |
+1 to graced's suggestion |
| 15:05 |
kmlussier |
OK, I'll do so. |
| 15:05 |
kmlussier |
Anything else before we wrap up? |
| 15:05 |
kmlussier |
Sorry to be 5 minutes late. |
| 15:06 |
|
tspindler left #evergreen |
| 15:06 |
DianeD |
thank you for doing this! |
| 15:06 |
kmlussier |
#endmeeting |
| 15:06 |
pinesol_green |
Meeting ended Wed May 10 15:06:18 2017 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:06 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2017/evergreen.2017-05-10-14.01.html |
| 15:06 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2017/evergreen.2017-05-10-14.01.txt |
| 15:06 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2017/evergreen.2017-05-10-14.01.log.html |
| 15:06 |
graced |
kmlussier++ |
| 15:06 |
ohiojoe |
kmlussier++ |
| 15:06 |
terran_ |
kmlussier++ thank you for getting this started up again! |
| 15:06 |
kmlussier |
Thanks everyone! |
| 15:06 |
ericar |
kmlussier++ |
| 15:07 |
gmcharlt |
kmlussier++ |
| 15:07 |
collum_ |
kmlussier++ |
| 15:14 |
jeffdavis |
gmcharlt: signed off on your signoff on bug 1552861 |
| 15:14 |
pinesol_green |
Launchpad bug 1552861 in Evergreen 2.11 "Incorrect datatype for Default Record Match Set org setting" [Low,Confirmed] https://launchpad.net/bugs/1552861 |
| 15:15 |
gmcharlt |
jeffdavis++ |
| 15:27 |
kmlussier |
bshum++ again for list of editors. |
| 15:27 |
kmlussier |
I discovered that the person whose email address I was unable to track down did not contribute content to the site. |
| 15:28 |
dbs |
I contacted one person who had made 0 contributions, oh well, good to get in contact with them again anyway :) |
| 15:28 |
JBoyer |
kmlussier, I meant to ask about that also, there were several people on there with 0 posts. They don't really have any say either way, so I'm not sure why they need be consulted at all. |
| 15:29 |
kmlussier |
JBoyer: I explained that above during the meeting. Those numbers were only for blog posts, but several of them had contributed content through WP pages. |
| 15:29 |
kmlussier |
Until bshum gave me his list, I didn't know which ones had edited page and which ones hadn't. |
| 15:30 |
kmlussier |
For example, I know Brent Mills was responsible for most of the content for the Hood River conference pages, even though his count was listed as 0. |
| 15:30 |
JBoyer |
Oops, haven't had a chance to read through the meeting yet. Sorry for the re-hash. :) |
| 15:31 |
kmlussier |
JBoyer: No worries. If I weren't on the web team, I probably wouldn't have read through it either. |
| 15:33 |
kmlussier |
JBoyer: But Shauna doesn't appear in bshum's list either, so I would say we don't need to worry about getting consent from her. |
| 15:35 |
JBoyer |
Ah, ok. I'll let that drop then. Thanks for letting me know! |
| 15:36 |
jeff |
anyone else run most of their ansible-playbooks twice, to ensure that your final run is all ok= and no changed/failed/unreachable? |
| 15:36 |
kmlussier |
JBoyer: Thanks for volunteering to help! |
| 15:36 |
jeff |
(with the obvious exception of "do something" playbooks like a restart playbook) |
| 15:36 |
kmlussier |
berick: Can I slap a pullrequest on bug 1631026 |
| 15:36 |
pinesol_green |
Launchpad bug 1631026 in Evergreen "Patron Registration: Circ is behind desk isn't hidden based on YAOUS" [Undecided,New] https://launchpad.net/bugs/1631026 |
| 15:40 |
JBoyer |
jeff, sometimes. I haven't marked everything that needs it as "un-changed" so there's a certain number that always change and I'm fine with that. (different numbers across the same role is a red flag though) |
| 15:46 |
berick |
kmlussier: looking... |
| 15:47 |
berick |
kmlussier: done |
| 15:47 |
kmlussier |
berick++ |
| 15:48 |
* kmlussier |
is having a bad technology day |
| 15:52 |
|
collum joined #evergreen |
| 16:07 |
|
ohiojoe joined #evergreen |
| 16:11 |
|
ohiojoe joined #evergreen |
| 16:12 |
|
ohiojoe joined #evergreen |
| 16:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:54 |
berick |
arg, so my problems last week (or thereabouts) with xulrunner not liking self-signed certs from nginx is just another symptom of bug #1648234 |
| 16:54 |
pinesol_green |
Launchpad bug 1648234 in Evergreen 2.12 "Internal Apache port leaks when using proxy" [Medium,Confirmed] https://launchpad.net/bugs/1648234 |
| 16:55 |
berick |
it was trying to add an exception for hostname:443 with a cert served from hostname:7443 though this was not visible to the user in the xul login window. |
| 16:55 |
* berick |
adds a note to the bug |
| 16:56 |
remingtron |
jlundgren: do I have your permission to add your name/email as the author for your Apache docs changes? (in bug 1673841) |
| 16:56 |
pinesol_green |
Launchpad bug 1673841 in Evergreen "Docs: Fix formatting on chapter Apache Access Handler" [Undecided,New] https://launchpad.net/bugs/1673841 - Assigned to Jeanette Lundgren (jlundgren) |
| 16:57 |
bshum |
berick: Good to know... fun times... |
| 16:57 |
bshum |
berick: We should get that merged :D |
| 16:57 |
bshum |
I read through the changes last night, but I wanted to test on a clean installation without proxy to be sure that all is well too |
| 16:57 |
bshum |
I'll try to give it a final whirl tonight and get it pushed |
| 16:59 |
berick |
bshum: that would be awesome. this thing's a bear. |
| 17:02 |
bshum |
berick: Indeed, perhaps it should be "High" importance |
| 17:03 |
bshum |
But in any case, soon, very soon. |
| 17:03 |
* bshum |
signs off for now to run some errands and then go home to get dinner. And test code! :D |
| 17:06 |
kmlussier |
@dessert |
| 17:06 |
* pinesol_green |
grabs some Coconut Cream Pie for kmlussier |
| 17:15 |
|
jvwoolf left #evergreen |
| 17:19 |
pinesol_green |
[evergreen|blake] Docs: Update MARC editor docs for web client - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=5729d40> |
| 17:31 |
|
AndroUser2 joined #evergreen |
| 18:07 |
gmcharlt |
bshum: please do test and signoff, but I want to do give final eyes on this one; assuming you test without finding issues tonight, I'll plan on testing and merging tomorrow |
| 18:29 |
|
AndroUser2 joined #evergreen |
| 18:49 |
bshum |
gmcharlt: Sure thing, I planned on checking with you on the rel_2_12 backport at the very least. But I'll just angle on testing then. |
| 18:50 |
* bshum |
doesn't like backporting too much |
| 22:20 |
|
genpaku joined #evergreen |
