Time |
Nick |
Message |
00:16 |
|
wsmoak joined #evergreen |
00:19 |
|
Stompro joined #evergreen |
00:19 |
|
eby joined #evergreen |
01:31 |
|
sandbergja2 joined #evergreen |
01:32 |
|
RBecker joined #evergreen |
03:00 |
|
StomproJ joined #evergreen |
05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
05:46 |
|
Stompro joined #evergreen |
06:02 |
|
wsmoak joined #evergreen |
07:10 |
|
rjackson_isl joined #evergreen |
08:41 |
|
mmorgan joined #evergreen |
08:53 |
|
Dyrcona joined #evergreen |
08:59 |
|
rlefaive joined #evergreen |
08:59 |
|
kmlussier joined #evergreen |
09:02 |
|
_adb joined #evergreen |
09:07 |
|
yboston joined #evergreen |
09:37 |
|
maryj joined #evergreen |
09:38 |
|
jvwoolf joined #evergreen |
10:41 |
|
bmills joined #evergreen |
10:43 |
Bmagic |
Anyone else wrestled with crontab and timezones? My action trigger cron seems to be inserting rows into ate with a runtime of 6 hours in the future. Which is exactly what time it would* be if it were UTC since our zone is -6. |
10:43 |
Bmagic |
Therefore, I believe that the system time in the cron environment is UTC |
10:44 |
berick |
cron should use whatever the OS uses.. 'date' will show the OS time zone |
10:45 |
Stompro |
Bmagic, I haven't run into problems like that. |
10:45 |
Bmagic |
yeah, that's what I thought, but that doesn't seem to be what is going on in practice. I have the OS timezone correct of course |
10:47 |
berick |
Bmagic: are the dates still correct? do they have timezone -0000 ? |
10:47 |
Bmagic |
I think that the cron is respecting my midnight runtime config 00 00 * * * but the script that runs inserts rows into the database with a run_time column of 6am, and it doesn't react to the trigger |
10:47 |
Bmagic |
in the database, the timezone is -6 for the tz part of the stamp (which is correct) |
10:48 |
berick |
ok, so the dates are actually wrong, not just in a different time zone |
10:48 |
Bmagic |
somewhere along the line, it thinks it's 6am when it's really midnight |
10:50 |
Bmagic |
postgres is configured to the correct zone, therefore when you do a query with time comparisons it's right. I think the perl script is inserting the rows specifying the run_time, and the perl script probably doesn't insert the time with the tz specified |
11:05 |
* csharp |
greets all y'all from Savannah, GA |
11:15 |
* berick |
waves at csharp |
11:23 |
|
kbutler joined #evergreen |
11:24 |
jeff |
@wunderground Savannah, GA |
11:24 |
pinesol_green |
jeff: Savannah, GA :: Overcast :: 59F/15C | Wednesday: Generally cloudy. High 66F. Winds light and variable. Wednesday Night: Mostly cloudy skies this evening will become partly cloudy after midnight. Low 49F. Winds light and variable. | Updated: 26m ago |
11:24 |
jeff |
must be nice this time of year, all that not-snow. |
11:25 |
jeff |
@wunderground --alerts KTVC |
11:25 |
pinesol_green |
jeff: Alerts: :: ...Winter Storm Warning in effect from midnight tonight to 3 PM EST Friday... The National Weather Service in Gaylord has issued a Winter Storm Warning...which is in effect from midnight tonight to 3 PM EST Friday. The Winter Storm Watch is no longer in effect. * Expect snow to intensify after midnight tonight with accumulating snowfall continuing through Friday. * The heaviest (2 more messages) |
11:29 |
berick |
@weather 27712 |
11:29 |
pinesol_green |
berick: Durham, NC :: Clear :: 52F/11C | Wednesday: Sunny. High 57F. Winds light and variable. Wednesday Night: Partly cloudy skies early will give way to cloudy skies late. Low 39F. Winds light and variable. | Updated: 24m ago |
12:02 |
pinesol_green |
[opensrf|Remington Steed] LP#1382038: Add instructions for implied download/unpack step - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=cd06277> |
12:02 |
pinesol_green |
[opensrf|Galen Charlton] LP#1382038: adjustments to download instructions - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=a1fe6e1> |
12:02 |
pinesol_green |
[opensrf|Galen Charlton] LP#1382038: clarify one step of installing websockets support - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=a3b2a15> |
12:12 |
|
finnx joined #evergreen |
12:23 |
|
brahmina joined #evergreen |
12:25 |
* mmorgan |
was reviewing the discussion of the display of account_adjustment payments in the patron record here: http://irc.evergreen-ils.org/evergreen/2016-10-14 |
12:26 |
mmorgan |
I don't see a launchpad bug that addresses the display issues. Am I missing it? If not, I'll open one. |
12:26 |
jeff |
i am not aware of one. |
12:27 |
jeff |
there was a good bit of discussion on this and related issues at the most recent hack-a-way. |
12:29 |
mmorgan |
jeff: yes, I was lurking a bit, and I know this is woven in with lp 1422379 |
12:29 |
pinesol_green |
Launchpad bug 1422379 in Evergreen "Move money.billing timestamps back to moment of fine" [Medium,Triaged] https://launchpad.net/bugs/1422379 - Assigned to Dan Wells (dbw2) |
12:30 |
mmorgan |
But I think addressing some of the display issues could go a long way toward helping staff better interpret complicated transactions. |
12:30 |
jeff |
i agree. |
12:31 |
* mmorgan |
will open a Launchpad bug. Maybe dbwells' branch-in-progress will find a home there :) |
12:34 |
sandbergja2 |
Hi everyone! The DIG meeting will take place in about 30 minutes. |
12:35 |
|
sandbergja joined #evergreen |
12:46 |
|
jihpringle joined #evergreen |
12:48 |
sandbergja |
Hi everyone, the DIG meeting will start in 12 minutes. |
12:49 |
dbwells |
mmorgan++ |
12:50 |
|
dluch joined #evergreen |
12:53 |
* kmlussier |
puts her DIG hat on. |
12:56 |
pinesol_green |
[opensrf|Bill Erickson] LP#1638651: example Nginx websockets/http(s) proxy config - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=ededc26> |
12:56 |
pinesol_green |
[opensrf|Galen Charlton] LP#1638651: add instructions for using NGINX - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=93da6fb> |
13:00 |
sandbergja |
#startmeeting Evergreen Documentation Interest Group (DIG) Meeting 2016-12-07 |
13:00 |
pinesol_green |
Meeting started Wed Dec 7 13:00:09 2016 US/Eastern. The chair is sandbergja. Information about MeetBot at http://wiki.debian.org/MeetBot. |
13:00 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
13:00 |
pinesol_green |
The meeting name has been set to 'evergreen_documentation_interest_group__dig__meeting_2016_12_07' |
13:00 |
sandbergja |
Welcome, everyone! |
13:00 |
sandbergja |
You can find today's agenda here: |
13:00 |
sandbergja |
#link https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meeting_20161207-agenda |
13:00 |
sandbergja |
#topic Introductions |
13:01 |
sandbergja |
Glad you are here; please let us know who you are! |
13:01 |
sandbergja |
#info sandbergja is Jane Sandberg, Linn-Benton Community College |
13:01 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka) |
13:01 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
13:01 |
kbutler |
#info kbutler is Kate Butler, Rodgers Memorial Library |
13:01 |
dluch |
#info dluch is Debbie Luchenbill, MOBIUS (Missouri Evergreen) |
13:02 |
sandbergja |
Thank you everyone for coming! |
13:02 |
sandbergja |
Did anybody have anything they'd like to add to the agenda? |
13:03 |
sandbergja |
If not, I think we can quickly go over old business, and then get to the main portion of today's discussion. |
13:04 |
sandbergja |
#topic Previous action items |
13:04 |
sandbergja |
#info jihpringle will research the state of missing RDA content |
13:04 |
|
Christineb joined #evergreen |
13:04 |
|
jlundgren joined #evergreen |
13:04 |
jihpringle |
it's on my to do list but unfortunately never seems to make it to the top |
13:05 |
sandbergja |
No worries! Should we just defer? |
13:05 |
jihpringle |
yes please |
13:05 |
sandbergja |
#action jihpringle will research the state of missing RDA content |
13:05 |
sandbergja |
#info kmlussier will document the general workflow for being DIG release coordinator |
13:05 |
kmlussier |
#info kmlussier has started to document the process at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:release_notes_process |
13:06 |
sandbergja |
Awesome! Thanks, kmlussier! |
13:06 |
kmlussier |
I documented how the acknowledgements are done, but I need to add other pieces. |
13:06 |
kmlussier |
In the meantime, I'm hoping to get a new volunteer to serve as release coordinator for the next release. I think I"ll have my hands full. |
13:06 |
sandbergja |
I'm sure! |
13:06 |
kmlussier |
I'll put out a call on the list, but if there is anyone interested, feel free to ping me. |
13:07 |
sandbergja |
kmlussier: Would you like me to put any action items down for you? |
13:07 |
kmlussier |
Sure, you can put me down for putting a call out on the list to find a volunteer to be DIG release coordinator. |
13:08 |
sandbergja |
#action kmlussier will put a call out on the list to find a volunteer to be DIG release coordinator |
13:08 |
sandbergja |
Thanks! |
13:08 |
sandbergja |
#info jihpringle will email yboston or mailing list with 2.10 docs that were completed |
13:09 |
jihpringle |
I thought I sent something after our upgrade in May |
13:09 |
sandbergja |
jihpringle: Should I put this for next time? |
13:09 |
sandbergja |
sorry, never mind! |
13:10 |
sandbergja |
Let's leave this be, then! Thanks, jihpringle! |
13:10 |
jihpringle |
np |
13:11 |
sandbergja |
#info Christineb will investigate creating a Youtube playlist that incorporates SITKA videos and videos from non-SITKA sources |
13:12 |
sandbergja |
Christineb: where you able to figure out more about Youtube playlists? |
13:12 |
sandbergja |
^were you able |
13:13 |
sandbergja |
We can just leave that action item for now. |
13:13 |
sandbergja |
#action Christineb will investigate creating a Youtube playlist that incorporates SITKA videos and videos from non-SITKA sources |
13:13 |
sandbergja |
#info sandbergja will conduct a doodle poll picking a date to work on 2.11 new features |
13:13 |
sandbergja |
I did this, but then didn't publicize the date very well. |
13:14 |
sandbergja |
Thanks to the few folks who did help with those docs regardless! |
13:14 |
sandbergja |
Perhaps we need to schedule another one, though? Thoughts? |
13:14 |
dluch |
Another date would probably be a good idea |
13:15 |
sandbergja |
Thanks, dluch! |
13:15 |
sandbergja |
Would anybody be able to work on this? |
13:16 |
jihpringle |
scheduling or the docs? |
13:16 |
sandbergja |
scheduling and publicizing a hack-a-way for 2.11 docs |
13:17 |
jihpringle |
I can run a doodle poll and then publicize it |
13:17 |
sandbergja |
sorry about not being clear! I don't want to burden anybody with doing all of the 2.11 docs! |
13:17 |
jihpringle |
when do we want to hold it? |
13:17 |
sandbergja |
thanks, jihpringle! |
13:17 |
kmlussier |
jihpringle++ |
13:17 |
sandbergja |
jihpringle++ |
13:18 |
jihpringle |
I don't know about others, but we're pretty booked up for December and January already |
13:19 |
dluch |
We are, too |
13:20 |
sandbergja |
And academic and school libraries will be on break for some of that time, too. :-( |
13:20 |
sandbergja |
It looks like mid-February is when we'd need to start documenting the 2.12 features |
13:20 |
sandbergja |
kmlussier: correct me if I'm wrong; I am not really up on the release process |
13:20 |
|
collum joined #evergreen |
13:20 |
kmlussier |
Not that I want to divide our attention too much, but is there any possibility of combining 2.11 features with a web client hack day? |
13:21 |
sandbergja |
That sounds reasonable to me |
13:21 |
kmlussier |
sandbergja: Yes, by February 22, we should know all the features that need to be documented for 2.12 |
13:22 |
sandbergja |
Would it be too much of a strain to do a 2.11/web client hack day in early February, and a 2.12 hack day in late February/early March? |
13:23 |
Christineb |
I missed this earlier - can we bump it to next agenda I will investigate before our next meeting - > Christineb will investigate creating a Youtube playlist that incorporates SITKA videos and videos from non-SITKA sources |
13:24 |
sandbergja |
Christineb++ |
13:24 |
sandbergja |
thanks; I'm excited to see what you find out |
13:24 |
jihpringle |
I think if we gave everyone lots of notice doing a 2.11/web client day in early February and a 2.12 hack day in early March would work |
13:24 |
kmlussier |
sandbergja: If there is a lot of advanced notice for both, I don't think it would be a strain. People can plan around dates if they know ahead of time that something is coming up. |
13:25 |
kmlussier |
Aw, jihpringle beat me to it. :) |
13:25 |
sandbergja |
Okay! Let's plan on that, then. :-) |
13:26 |
jihpringle |
I'll send out doodle polls for both today and ask people to people to respond by Dec 21st |
13:26 |
sandbergja |
jihpringle++ |
13:26 |
sandbergja |
#action jihpringle will schedule and publicize a 2.11/web client hack day for early February |
13:26 |
jihpringle |
then we can have the days in the calendar before the end of December |
13:26 |
sandbergja |
that would be excellent |
13:26 |
dluch |
jihpringle++ |
13:27 |
sandbergja |
#info yboston will email Galen to give remingtron and sandbergja access to DIG test server |
13:27 |
sandbergja |
This is done. |
13:27 |
sandbergja |
yboston++ gmcharlt++ |
13:27 |
sandbergja |
Thanks for the updates, everyone! |
13:27 |
sandbergja |
#topic Progress on documenting new features in Evergreen 2.11 |
13:27 |
sandbergja |
I think we have this pretty well sorted out, so I'll move on. |
13:28 |
sandbergja |
#topic Finding a new DIG Facilitator |
13:28 |
sandbergja |
Let me start out by saying :-( |
13:28 |
sandbergja |
And that I miss yboston already! |
13:29 |
sandbergja |
What should the process be for finding a new DIG Facilitator? |
13:29 |
sandbergja |
Should we put a call out to the email lists, similar to what kmlussier is doing for the DIG release coordinator? |
13:30 |
kmlussier |
In some ways, I'm inclined on holding off on my call until we have a DIG facilitator. I think it's more important that we find someone to lead the group first. |
13:32 |
kmlussier |
I just looked at the e-mail list archive to see how it was handled before. It looks like Karen tapped yboston to be facilitator before she notified that she had to step down. |
13:32 |
kmlussier |
No, wait, I'm wrong on that. |
13:33 |
kmlussier |
He had already been filling in for her while she was out on maternity leave. I think a more formal call on the DIG list would make sense. |
13:33 |
kmlussier |
Unless there is anyone here who would like to volunteer now? |
13:34 |
kmlussier |
<crickets> |
13:34 |
sandbergja |
It was worth a try, though! |
13:34 |
sandbergja |
I would be happy to put out a call |
13:35 |
sandbergja |
And I can also facilitate meetings until we have a more permanent DIG facilitator, if folks would be okay with that |
13:35 |
kmlussier |
Yes, that makes sense. In the meantime, people can feel free to poke other people directly if they think they would be good for the role. |
13:35 |
kmlussier |
sandbergja: No arguments from me! :) |
13:37 |
pinesol_green |
[opensrf|Galen Charlton] LP#1648188: example HAProxy configuration - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=b1d19c8> |
13:37 |
sandbergja |
#action sandbergja will put out a formal call for DIG facilitator |
13:37 |
kmlussier |
I'll also hold off on the release coordinator call. I don't want to put out too many calls for volunteers at the same time and possibly distract somebody's attention away from the facilitator positions. |
13:37 |
sandbergja |
Fair enough! |
13:37 |
dluch |
Thanks for facilitating us for now, sandbergja! |
13:37 |
sandbergja |
No problem! |
13:37 |
dluch |
sandbergja++ |
13:37 |
kbutler |
sandbergja++ |
13:37 |
jihpringle |
sandbergja++ |
13:37 |
kmlussier |
sandbergja++ |
13:38 |
sandbergja |
Thanks, everyone! |
13:38 |
sandbergja |
#topic Progress on Documentation-related bugs in launchpad |
13:38 |
sandbergja |
Switching gears a bit |
13:39 |
sandbergja |
This is more for my information. Is anybody super-actively working on these? |
13:39 |
sandbergja |
#link https://bugs.launchpad.net/evergreen/+bugs?field.tag=documentation |
13:40 |
sandbergja |
And what should their priority be compared to all the other stuff that DIG works on? |
13:40 |
kmlussier |
No. It might be nice to highlight those for Bug Squashing day in case there are any DIG folks who want to help out on the doc side of things. |
13:41 |
sandbergja |
So we can informally put out the word that "there are docs bugs too" next time the bug squashing day publicity comes around? |
13:41 |
kmlussier |
It might be a good start. |
13:42 |
sandbergja |
That sounds good to me! |
13:42 |
sandbergja |
Thanks for the info. |
13:42 |
sandbergja |
#topic Progress on Web Client docs |
13:42 |
* kmlussier |
sometimes files those bugs just as a reminder that there is a simple doc change she wants to change, but it doesn't help. |
13:43 |
sandbergja |
Thanks again to jihpringle for helping us get some time scheduled to work on these |
13:43 |
sandbergja |
Does anybody have some updates or observations on Web client docs? |
13:44 |
kmlussier |
I think we're getting to the point now, with the web client, that we really need to buckle down on getting these docs done. The February hack date will help. |
13:44 |
kmlussier |
But I'm guessing that we'll want to include it in the 2.12 hack date too just because we're hoping the web client gets much production use for the next release. |
13:46 |
sandbergja |
That's exciting! |
13:46 |
dluch |
I agree, kmlussier |
13:46 |
jihpringle |
do we have any web docs publicly accessible currently? |
13:46 |
sandbergja |
jihpringle: a few |
13:46 |
kmlussier |
This could probably be updated - https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:webclient |
13:47 |
sandbergja |
#link http://docs.evergreen-ils.org/2.11/_web_client_preview.html |
13:47 |
sandbergja |
Here's a question: how much documentation do you think a library would need when adopting the Web client after using the XUL client? |
13:48 |
kmlussier |
sandbergja: I could probably take an action item to update the web client doc needs page. I spend a lot of time in the web client. |
13:48 |
sandbergja |
kmlussier++ |
13:48 |
sandbergja |
A lot of screens are very similar in XUL client vs. Web client |
13:48 |
kmlussier |
sandbergja: A lot of the interfaces are very similar to the xul ones, so they may not need the docs to transition. But there are a few others that are different, particularly in cataloging. |
13:49 |
jihpringle |
this may not be a question we're ready to answer, but are we planning to a have a separate book for the webclient or have the webclient docs within the 2.12 book with the staff client docs? |
13:49 |
kmlussier |
I'm thinking the Holdings View is a bit different from holdings maintenance. Also, the volume/copy editor has a lot of differences. |
13:49 |
sandbergja |
#action kmlussier will update the web client doc needs page |
13:50 |
kmlussier |
jihpringle: Eventually, it should take the place of the staff client docs. The current structure, IMO, should be temporary while people are still moving from one to the other. |
13:50 |
sandbergja |
That's helpful; thanks all for the conversation. |
13:50 |
sandbergja |
#topic Progress on Docs Reorganization Project |
13:51 |
sandbergja |
We actually have some reorganized docs! |
13:51 |
sandbergja |
These are by no means complete, just conversation starters to get people excited about the project again. :-) |
13:51 |
sandbergja |
Here's a manual for local sysadmins: |
13:51 |
kmlussier |
Yay! sandbergja++ |
13:51 |
sandbergja |
#link http://docs-testing.evergreen-ils.org/docs/reorg/staffclient_sysadmin/ |
13:51 |
sandbergja |
And a small one for front-line circ staff: |
13:52 |
sandbergja |
#link http://docs-testing.evergreen-ils.org/docs/reorg/circulation/ |
13:52 |
sandbergja |
I'm hoping to get the Docs Reorg group back together at some point to look these over, and try to figure out where to go from here |
13:53 |
sandbergja |
But am also more than happy to take suggestions now as well. :-) |
13:54 |
|
bmills joined #evergreen |
13:54 |
kmlussier |
At a first glance, it looks good, but I would need more time to look at it before giving specific feedback. |
13:55 |
sandbergja |
That makes sense. :-) |
13:55 |
sandbergja |
Did anybody have any topics for our last five minutes? |
13:56 |
|
tspindler joined #evergreen |
13:56 |
sandbergja |
Thanks again to everybody for all the crucial documentation work you do! |
13:57 |
sandbergja |
And for making time to join today's meeting |
13:57 |
sandbergja |
Best wishes for the rest of the week! |
13:57 |
dluch |
Thank you, sandbergja! |
13:57 |
sandbergja |
#endmeeting |
13:57 |
pinesol_green |
Meeting ended Wed Dec 7 13:57:37 2016 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
13:57 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-12-07-13.00.html |
13:57 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-12-07-13.00.txt |
13:57 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-12-07-13.00.log.html |
13:57 |
jihpringle |
sandbergja++ |
13:57 |
dluch |
sandbergja++ |
13:58 |
kmlussier |
sandbergja++ |
13:58 |
sandbergja |
jihpringle: I just saw that you sent out those Doodle polls already! |
13:58 |
sandbergja |
jihpringle++ |
13:58 |
kbutler |
sandbergja++ jihpringle++ |
13:58 |
dluch |
jihpringle++ |
14:00 |
kmlussier |
jihpringle++ |
14:10 |
|
dmband33 joined #evergreen |
14:13 |
|
dmband33 left #evergreen |
14:23 |
berick |
gmcharlt++ proxy configs |
14:28 |
|
DPearl joined #evergreen |
14:58 |
|
abowling joined #evergreen |
15:00 |
gmcharlt |
dev meeting in ONE MINUTE |
15:03 |
gmcharlt |
OK, let's do this thing |
15:03 |
kmlussier |
gmcharlt++ |
15:04 |
gmcharlt |
#startmeeting Evergreen Development meeting, 7 December 2016 |
15:04 |
pinesol_green |
Meeting started Wed Dec 7 15:04:01 2016 US/Eastern. The chair is gmcharlt. Information about MeetBot at http://wiki.debian.org/MeetBot. |
15:04 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
15:04 |
pinesol_green |
The meeting name has been set to 'evergreen_development_meeting__7_december_2016' |
15:04 |
gmcharlt |
#info Agenda https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2016-12-07 |
15:04 |
gmcharlt |
#topic Introductions |
15:04 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
15:04 |
gmcharlt |
#info gmcharlt = Galen Charlton, Equinox's House of Cat and Commit Herding |
15:04 |
abowling |
#info abowling = Adam Bowling, Emerald Data Networks |
15:04 |
JBoyer |
#info JBoyer is Jason Boyer, Indiana State Library Evergreen Indiana |
15:04 |
jeff |
#info jeff == Jeff Godin, Traverse Area District Library (TADL) |
15:05 |
berick |
#info berick Bill Erickson King County Library (KCLS) |
15:05 |
remingtron |
#info remingtron = Remington Steed, Hekman Library (Calvin College) |
15:05 |
dbwells |
#info dbwells = Dan Wells, Hekman Library (Calvin College) |
15:07 |
gmcharlt |
OK, moving on; feel free to continue to introduce yourself |
15:07 |
gmcharlt |
#topic Action items from last meeting |
15:07 |
gmcharlt |
#info gmcharlt did not cut the OpenSRF 2.5-alpha release yet, but is typing release notes AS WE SPEAK |
15:07 |
gmcharlt |
#action gmcharlt will release OpenSRF 2.5-alpha today (7 December 2016) |
15:08 |
gmcharlt |
the 2.11 release announcement was blogged |
15:08 |
gmcharlt |
kmlussier sent out the press release |
15:08 |
gmcharlt |
the RM nominations and election took place |
15:08 |
gmcharlt |
kmlussier++ |
15:09 |
gmcharlt |
and as it's a carry-over |
15:09 |
Bmagic |
#info Bmagic = Blake GH, MOBIUS |
15:09 |
gmcharlt |
#gmcharlt and Dyrcona to create guidelines on the wiki to determine what is a bug fix vs. new feature. |
15:09 |
gmcharlt |
-- in particular, to suggest guidelines for what should be backported |
15:09 |
gmcharlt |
so, I think that does it for action items from back in the mists of time |
15:09 |
gmcharlt |
so moving on |
15:10 |
gmcharlt |
#topic OpenSRF release info |
15:10 |
gmcharlt |
#info OpenSRF 2.5 alpha to be cut on 7 December |
15:10 |
gmcharlt |
so, with respect to the alpha, there are some things in particular I'd like to request testing for |
15:10 |
gmcharlt |
1. the proxy configurations |
15:10 |
jeff |
TZ changes? |
15:10 |
gmcharlt |
2. bundling and chunking |
15:10 |
jeff |
er, you're listing. |
15:11 |
gmcharlt |
3. TZ changes |
15:11 |
gmcharlt |
and there's a potential decision point for us |
15:11 |
gmcharlt |
namely, do we want to consider having use of a proxy be a default recommended configuration? |
15:12 |
gmcharlt |
and whether or not we do that, I'm thinking that before 2.5.0, we should make the default websockets port become a configure-time parameter |
15:12 |
gmcharlt |
thoughts? |
15:12 |
jeff |
are you making a distinction between recommendation and requirement? |
15:13 |
gmcharlt |
jeff: I am, I think |
15:13 |
gmcharlt |
"requirement" to me suggests that we bite the bullet and have Evergreen users move over to that configuration |
15:13 |
gmcharlt |
but... that's a mare's nest |
15:13 |
Dyrcona |
#info Dyrcona = Jason Stephenson, C/W MARS |
15:13 |
jeff |
+1 to making websockets port be not-hardcoded |
15:13 |
JBoyer |
I think in the long run it would be preferable to shave some weight off of the perl modules loaded in apache processes so it's not necessary at all, but that's not going to be done soon. |
15:13 |
jeff |
+1 to recommending proxy |
15:13 |
JBoyer |
also +1 to build time port settings |
15:13 |
jeff |
+1 to recommending proxy for production |
15:14 |
jeff |
(clarifying/qualifying my previous +1) |
15:14 |
berick |
+1 to moving toward proxy recommendation. i know of at least one bug using the proxy w/ EG, where a redirectmatch sends the ser from /eg/staff to 7443:/eg/staff/ |
15:14 |
berick |
i.e. the internal port number leaks |
15:14 |
gmcharlt |
whoopsie |
15:14 |
gmcharlt |
and that's certainly something to nail down before .0 |
15:15 |
berick |
so, it might need a little wider use before full blown recommendation |
15:15 |
berick |
gmcharlt: to clarify, it's really an EG bug, but yea.. |
15:15 |
gmcharlt |
yeah, most of the question of full-blown recommendation would be on EG's end, particular for install documentatation |
15:15 |
gmcharlt |
on the plus side, we have time before 2.12 |
15:16 |
gmcharlt |
any other questions or thoughts on OpenSRF? |
15:16 |
berick |
yeah, and fwiw I've been using the osrf proxy for a while now and that's the only issue i've run into |
15:16 |
gmcharlt |
cool |
15:16 |
gmcharlt |
the haproxy config will require more testing, but it's what I"ll be running |
15:17 |
gmcharlt |
ok, |
15:17 |
gmcharlt |
moving on |
15:17 |
gmcharlt |
#topic Evergreen releases |
15:17 |
bshum |
Would it be good to make websockets required, rather than just optional in a future OpenSRF release? |
15:17 |
bshum |
oops heh |
15:17 |
dbwells |
One other questions related to chunking/bundling, Bmagic a few weeks back hit what appeared to be an incompatibility with that change in EG master. It's probably possible to fix in a backwards compat. way, but regardless, are we assuming OSRF 2.5 will be recommended for EG 2.12+, or do we need it to work with other current releases? |
15:18 |
gmcharlt |
it would be a niceness, but not required, that it work with current releases |
15:18 |
gmcharlt |
dbwells: do you happen to have a bug # for that? |
15:19 |
dbwells |
gmcharlt: I will find or make one and get back to you. |
15:19 |
gmcharlt |
but unless something weird happens, I'm assuming that Evergreen 2.12 would require OpenSRF 2.5 |
15:19 |
gmcharlt |
dbwells++ |
15:19 |
gmcharlt |
any other OpenSRF stuff? |
15:20 |
Dyrcona |
I'd say if there is a backwards compatibility issue that can't be resolved, then we need to support 2.4 until it is resolved or 2.11 is no longer supported. |
15:20 |
gmcharlt |
that strikes me as easy enough |
15:20 |
gmcharlt |
#info Evergreen 2.11.1 and 2.10.8 was released on 16 November 2016 |
15:20 |
Bmagic |
dbwells: could have been xenial support |
15:21 |
gmcharlt |
kmlussier: anything you want to say about 2.12 at the moment? |
15:22 |
kmlussier |
#info 2.12 schedule is set - http://markmail.org/message/4jmxknraen6k7nqr |
15:22 |
bshum |
Bmagic: I was just thinking that if we do decide to keep OpenSRF 2.4 series around instead of going for 2.5, we should reconsider the decision not to backport Xenial support to that |
15:22 |
kmlussier |
#info Roadmap entries can be added to the wiki at https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap:2.12 |
15:23 |
kmlussier |
As I mentioned at the hack-a-way, I would like to schedule some web client hacking days to help us get more work done on the browser client. |
15:23 |
kmlussier |
I meant to schedule them as soon as I got back, but now a month has flown by. A question I have for the run, is it doable to try to squeeze one in before the holidays or should I plan on a January date? |
15:25 |
* gmcharlt |
is thinking January |
15:26 |
kmlussier |
OK, I'll proceed with a January date then. |
15:26 |
kmlussier |
Also, I think bug 1642054 is the chunking issue mentioned by dbwells above. |
15:26 |
pinesol_green |
Launchpad bug 1642054 in Evergreen "References to chunking need to be renamed to bundling" [High,New] https://launchpad.net/bugs/1642054 |
15:26 |
dbwells |
gmcharlt: found the bug, #1642054 . kmlussier++ |
15:26 |
dbwells |
heh |
15:26 |
kmlussier |
dbwells: Jinx! |
15:26 |
gmcharlt |
dbwells: kmlussier: thanks |
15:27 |
gmcharlt |
and at first blush, I think these can be readily resolved in such a way that 2.10/2.11 can run on top of OpenSRF 2.5.x |
15:27 |
gmcharlt |
and for that matter, I'll mark that as a blocker for the OpenSRF 2.5-beta/2.5.0 release |
15:28 |
gmcharlt |
kmlussier: anythhing else for the Evergreen release topic? |
15:28 |
kmlussier |
Nope |
15:28 |
gmcharlt |
#topic Hatch |
15:29 |
berick |
that's me |
15:29 |
berick |
i think I said it all in the agenda.. basically, would like to get other eyes on the code / behavior |
15:29 |
berick |
help me flesh out the dev install docs and make sure we're all still on the same page |
15:30 |
gmcharlt |
#info Hatch omnibus bug https://bugs.launchpad.net/evergreen/+bug/1646166 |
15:30 |
pinesol_green |
Launchpad bug 1646166 in Evergreen "Hatch 2.12 Omnibus" [Undecided,New] - Assigned to Bill Erickson (berick) |
15:30 |
jeff |
I'm still quite interested in that. |
15:30 |
jeff |
So, I'll volunteer my eyes. |
15:30 |
kmlussier |
I can test installing on Linux |
15:30 |
berick |
i have one final note to add to the install docs, the final "here's how you actually use it" bit |
15:31 |
gmcharlt |
I can take a look at OS X installation |
15:31 |
berick |
but that'll just take a sec |
15:31 |
berick |
(and I can do that today) |
15:31 |
berick |
thanks jeff kmlussier gmcharlt |
15:31 |
berick |
holler w/ any problems or confusion |
15:31 |
berick |
gmcharlt: as noted, the mac stuff will be very at-your-own-risk at this point |
15:31 |
berick |
well.. s/risk/you figure it out/ |
15:32 |
berick |
but I have made it work |
15:32 |
gmcharlt |
"let's see, should I push that largish button that has an inviting shade of scarlet?" |
15:33 |
berick |
always |
15:33 |
gmcharlt |
:) |
15:33 |
gmcharlt |
anything else for Hatch? |
15:33 |
berick |
i think that's it from me |
15:34 |
gmcharlt |
on to new business |
15:34 |
gmcharlt |
#topic Documenting the release process |
15:35 |
kmlussier |
I added that topic to the agenda to update y'all on the status of this, which was discussed at the hack-a-way. |
15:35 |
kmlussier |
I am using https://wiki.evergreen-ils.org/doku.php?id=dev:evergreen:release_checklist, which was developed back in the 2.2 days, as a starting point to outline who does what in the release process. |
15:36 |
kmlussier |
I think we could also use this page to link to other wiki pages we have with more detailed instructions on how to build a release, how to do release notes, who to send pr to, etc. |
15:37 |
kmlussier |
It's just a draft now, but if anyone has feedback, you know where to find me. |
15:37 |
kmlussier |
Also, I just wanted to mention there are some roles there, like bug wrangler, where I don't think we have designated people. |
15:38 |
kmlussier |
I don't know if we should fold those tasks into other roles or if we should try to get new volunteers to help with some of these tasks. |
15:40 |
kmlussier |
But maybe I can flesh that out more with the other folks who volunteered to work on this. |
15:40 |
gmcharlt |
gut feeling -- the more humans involved, the more we will need not only roles, but a specific timeframe |
15:41 |
gmcharlt |
e.g., something along the lines of D-Day - 3: release notes finalized |
15:41 |
gmcharlt |
D-Day - 1: tarballs built |
15:41 |
gmcharlt |
and so forth |
15:41 |
kmlussier |
Sure, I think that's doable. |
15:42 |
kmlussier |
When we talked about this at the hack-a-way, I think we were also saying that it might not be one point person, but a group of known people who could be called upon when help is needed. |
15:42 |
gmcharlt |
another suggestion (maybe nitpick) - perhaps the checklist should be put in the order that steps need to take place |
15:42 |
gmcharlt |
e.g., since the release notes are included in the tarball, they need to be finalized before the buildmasters can bild |
15:43 |
kmlussier |
sure |
15:43 |
gmcharlt |
kmlussier: when and how would be the best way to get feedback to you? |
15:44 |
kmlussier |
When could be the end of the month? That will give me time to improve it before the next dev meeting. |
15:44 |
kmlussier |
How could be in IRC or e-mail. But I won't be around towards the end of the month, so e-mail may work better. |
15:45 |
gmcharlt |
open-ils-dev, or to you directly? |
15:45 |
kmlussier |
Why don't you give me an action item to post something to open-ils-dev to solicit feedback. Then, more discussion can happen there. |
15:46 |
gmcharlt |
I can do that |
15:46 |
gmcharlt |
#action kmlussier will post to open-ils-dev soliciting feedback on the release process documentation |
15:47 |
gmcharlt |
anything else on this topic? |
15:47 |
kmlussier |
nope |
15:47 |
gmcharlt |
OK, that takes us to the end of the agenda, but before we end the meeting, is there anything else that somebody woul like to raise for immediate consideration? |
15:48 |
gmcharlt |
going once |
15:48 |
gmcharlt |
going twice |
15:48 |
gmcharlt |
gone |
15:49 |
gmcharlt |
now go forth and code and document for great justice! |
15:49 |
gmcharlt |
#endmeeting |
15:49 |
pinesol_green |
Meeting ended Wed Dec 7 15:49:08 2016 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
15:49 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-12-07-15.04.html |
15:49 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-12-07-15.04.txt |
15:49 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-12-07-15.04.log.html |
15:49 |
kmlussier |
gmcharlt++ |
15:49 |
berick |
gmcharlt++ |
15:50 |
dbwells |
gmcharlt++ |
15:50 |
berick |
kmlussier: gmcharlt jeff: i pushed the last bit of docs to the hatch branch that I had planned. |
15:51 |
gmcharlt |
berick++ |
15:51 |
Bmagic |
berick++ |
15:51 |
kmlussier |
berick++ |
15:51 |
Bmagic |
kmlussier++ |
15:51 |
Bmagic |
gmcharlt++ |
15:53 |
JBoyer |
gmcharlt++ |
15:56 |
* csharp |
shows up for the dev meeting: HI GUYS, DID I MISS ANYTHING? |
15:56 |
gmcharlt |
csharp: you get to do ALL THE ACTION ITEMS |
15:56 |
gmcharlt |
just so you know |
15:56 |
* csharp |
just got VOLUNTOLD |
15:57 |
abowling |
gmcharlt++ |
16:05 |
|
tspindler left #evergreen |
16:05 |
|
Shae joined #evergreen |
16:05 |
|
miker joined #evergreen |
16:05 |
|
graced joined #evergreen |
16:07 |
|
jyorio joined #evergreen |
16:08 |
|
rhamby joined #evergreen |
16:10 |
Bmagic |
charp++ |
16:11 |
remingtron |
sandbergja++ #reviving the docs brigade |
16:25 |
|
akilsdonk joined #evergreen |
16:37 |
|
abneiman joined #evergreen |
16:45 |
|
barbara joined #evergreen |
16:51 |
|
bmills1 joined #evergreen |
17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:06 |
|
mmorgan left #evergreen |
17:14 |
|
rlefaive_ joined #evergreen |
17:21 |
|
jvwoolf left #evergreen |
17:28 |
Bmagic |
Evergreen rocks and csharp is the spy! |
17:28 |
Bmagic |
FYI |
17:29 |
gmcharlt |
OpenSRF-2.5.0-alpha is now available from https://evergreen-ils.org/opensrf-downloads/ |
17:46 |
|
bmills joined #evergreen |
17:49 |
dbwells |
gmcharlt++ |
19:17 |
|
abowling left #evergreen |
20:45 |
|
bmills joined #evergreen |
20:48 |
|
finnx1 joined #evergreen |
21:35 |
|
Shae joined #evergreen |
21:35 |
|
miker joined #evergreen |
22:30 |
|
book` joined #evergreen |
23:06 |
|
StomproJ joined #evergreen |
23:57 |
|
Stompro joined #evergreen |