| Time |
Nick |
Message |
| 05:24 |
|
khuckins joined #evergreen |
| 05:59 |
|
khuckins joined #evergreen |
| 06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 06:00 |
|
khuckins_ joined #evergreen |
| 06:02 |
|
khuckin__ joined #evergreen |
| 07:25 |
|
rjackson_isl_hom joined #evergreen |
| 07:25 |
|
rjackson_isl_hom joined #evergreen |
| 08:10 |
|
mantis1 joined #evergreen |
| 08:46 |
|
rfrasur joined #evergreen |
| 08:47 |
|
mmorgan joined #evergreen |
| 08:50 |
|
collum joined #evergreen |
| 08:56 |
|
Dyrcona joined #evergreen |
| 10:23 |
|
Cocopuff2018 joined #evergreen |
| 10:39 |
|
stephengwills joined #evergreen |
| 10:46 |
Dyrcona |
Hmm. Schedule something for 11:30 am or just do it myself? |
| 10:46 |
Dyrcona |
@decide at or manual |
| 10:46 |
pinesol |
Dyrcona: That's a tough one... |
| 10:55 |
Dyrcona |
Bleh.. Tryina test a rsync command and looks like it ignored the -n option. |
| 10:56 |
Dyrcona |
So, a couple of files got copied early. Hope that didn't break anything. If it did, guess I'll hear about it. |
| 10:57 |
Dyrcona |
Things are working for me, so guess it's no big deal |
| 11:03 |
Dyrcona |
berick: If I'm using rsync to update /openils/var/web/eg2/en-US/ should I use --delete to remove older versions of some of the files? |
| 11:04 |
berick |
Dyrcona: you certainly can, but you may want to ensure the new index.html is in place on all servers first, so nothing tries to grab the older files. |
| 11:06 |
berick |
elg. distribute new hashed js files -> distribute new index.html -> delete old hashed js files. |
| 11:06 |
berick |
s/elg/eg/ |
| 11:06 |
berick |
or do it all at once if it's pratically instantaneous ;) |
| 11:06 |
|
dbwells joined #evergreen |
| 11:06 |
Dyrcona |
berick: Thanks. That is what I thought, so `rsync -av --delete Open-ILS/web/eg2/ /openils/var/web/eg2/` should be OK. |
| 11:08 |
|
dbwells_ joined #evergreen |
| 11:12 |
|
jihpringle joined #evergreen |
| 11:46 |
|
jvwoolf joined #evergreen |
| 12:10 |
|
khuckins joined #evergreen |
| 12:40 |
|
Christineb joined #evergreen |
| 13:08 |
csharp |
so... what is the correct way for resetting a password from the DB end now that we're using actor.passwd? |
| 13:08 |
csharp |
I've tried actor.migrate_passwd after changing actor.usr.passwd (this is an older account) |
| 13:08 |
csharp |
then I tried actor.set_passwd |
| 13:09 |
berick |
csharp: there's a new db func just for that... |
| 13:09 |
csharp |
but it's not allowing login afterwards |
| 13:09 |
berick |
actor.change_password |
| 13:09 |
csharp |
aah |
| 13:10 |
csharp |
berick++ # thanks! |
| 13:11 |
Dyrcona |
csharp: I have a db function for that. |
| 13:11 |
|
khuckins joined #evergreen |
| 13:11 |
Dyrcona |
csharp: https://pastebin.com/YTLh7pC9 |
| 13:12 |
rhamby |
yeah, that's one I think most of us did of us did on our own so it made sense to make make it native |
| 13:12 |
Dyrcona |
Oh, ha! |
| 13:12 |
Dyrcona |
berick++ |
| 13:14 |
Dyrcona |
actor.change_password postdates our production environment... |
| 13:15 |
Dyrcona |
Looks like it is new in 3.6. |
| 13:29 |
rhamby |
yep |
| 13:30 |
csharp |
Dyrcona++ # thanks! |
| 13:37 |
Dyrcona |
csharp: NP, but NB that the actor.change_password function is more accurate than mine. I'm considering backporting it and dropping ours from the database, though I only really use it for the training server. |
| 13:44 |
rhamby |
it should pick pretty cleanly, it's self contained as I recall |
| 13:48 |
Dyrcona |
Yeah, and I can also just checkout the db upgrade script, since that's all I really need. |
| 13:54 |
JBoyer |
Dev meeting in 5 minutes |
| 13:55 |
berick |
JBoyer: hm, 3pm? |
| 13:55 |
Dyrcona |
It's at 2:00? |
| 13:55 |
Dyrcona |
What berick said. |
| 13:55 |
JBoyer |
I *meant* to say, dev meeting in 65 minutes. |
| 13:55 |
JBoyer |
Obviously. :D |
| 13:55 |
Dyrcona |
:) |
| 13:55 |
JBoyer |
berick++ |
| 13:55 |
JBoyer |
Dyrcona++ |
| 13:56 |
Dyrcona |
JBoyer++ # For testing us. :) |
| 13:56 |
stephengwills |
that pesky SIX key! |
| 14:06 |
|
sandbergja_ joined #evergreen |
| 14:23 |
mantis1 |
Question about the autorenewal feature. Is there a way to block autorenewals from happening if there is a hold on said item? |
| 14:24 |
mantis1 |
I tested it with both a copy and bib level hold for two separate items, and autorenewals went through. |
| 14:41 |
jeff |
I don't know that there's an autorenew-specific block, but there's an org unit setting for blocking renewals when there's a hold, and there's also the option of defining a minimum hold:copy ratio as part of your circ policy. In theory the latter gives you more nuanced control, but I can't confirm that because we're not currently using it. |
| 14:47 |
|
alynn26 joined #evergreen |
| 14:52 |
|
terranm joined #evergreen |
| 14:56 |
mmorgan |
mantis1: In our system, autorenewals are blocked if there is a hold. Maybe an ou setting? |
| 14:56 |
* mmorgan |
looks |
| 14:57 |
Dyrcona |
There is a setting to block renewals when there are holds. Forget what it is called. |
| 14:57 |
mmorgan |
"Block Renewal of Items Needed for Holds", circ.block_renews_for_holds, we have it set to TRUE for the consortium |
| 15:02 |
JBoyer |
What time is it? |
| 15:02 |
JBoyer |
Dev time! |
| 15:02 |
gmcharlt |
MEETING TIME |
| 15:02 |
JBoyer |
gmcharlt++ on top of the call and response |
| 15:02 |
JBoyer |
#startmeeting 2020-02-02 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-02-02 |
| 15:02 |
pinesol |
Meeting started Tue Feb 2 15:02:55 2021 US/Eastern. The chair is JBoyer. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:02 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 15:02 |
|
Topic for #evergreen is now (Meeting topic: 2020-02-02 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-02-02) |
| 15:02 |
pinesol |
The meeting name has been set to '2020_02_02___developer_meeting__agenda_available_at_https___wiki_evergreen_ils_org_doku_php_id_dev_meetings_2021_02_02' |
| 15:03 |
JBoyer |
#topic Introductions |
| 15:03 |
|
Topic for #evergreen is now Introductions (Meeting topic: 2020-02-02 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-02-02) |
| 15:03 |
JBoyer |
maek info |
| 15:03 |
JBoyer |
#info JBoyer = Jason Boyer, Equinox |
| 15:03 |
dluch |
#info dluch = Debbie Luchenbill, MOBIUS (DIG facilitator) |
| 15:03 |
jeff |
#info jeff = Jeff Godin, Traverse Area District Library (TADL) |
| 15:03 |
phasefx |
#info phasefx = Jason Etheridge, Equinox |
| 15:03 |
abneiman |
#info abneiman = Andrea Buntz Neiman, Equinox |
| 15:03 |
berick |
#info berick, Bill Erickson |
| 15:03 |
mmorgan |
#info mmorgan = Michele Morgan, NOBLE |
| 15:03 |
sandbergja |
#info sandbergja = Jane Sandberg, Linn-Benton Community College |
| 15:04 |
stephengwills |
#info stephengwills => Steve Wills, Maine Balsam Library Consortium |
| 15:04 |
gmcharlt |
#info gmcharlt = Galen Charlton, Equinox (partial attentino) |
| 15:04 |
JBoyer |
Others feel free to announce yourself when popping in. |
| 15:04 |
JBoyer |
#topic Action Items from Last Meeting |
| 15:04 |
|
Topic for #evergreen is now Action Items from Last Meeting (Meeting topic: 2020-02-02 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-02-02) |
| 15:04 |
terranm |
#info terranm = Terran McCanna, PINES |
| 15:04 |
JBoyer |
1. JBoyer will poll the community about possible dev meeting times |
| 15:05 |
Dyrcona |
#info Dyrcona = Jason Stephenson CW MARS, Inc. |
| 15:05 |
JBoyer |
This was done to varying levels of effectiveness |
| 15:05 |
JBoyer |
Poll is still open at https://forms.gle/ypTx2zqLbW7eVoj99 if you have not yet answered. |
| 15:05 |
csharp |
#info csharp = Chris Sharp, GPLS |
| 15:05 |
mrisher |
#info mrisher = Mike Risher, Catalyte / KCLS |
| 15:06 |
JBoyer |
I should have remembered to make a ~5-10 minute announcement less than 60 minutes out. :) (I am glad to see so many folks make it today) |
| 15:07 |
berick |
a reminder reminder |
| 15:07 |
JBoyer |
The results of the poll are basically that the second week of the month works for everyone, and we'll probably be trying the Second Tuesday at 2pm Eastern for a while |
| 15:08 |
JBoyer |
The Discord person can get off my lawn though. |
| 15:08 |
JBoyer |
(I kid. ;) ) |
| 15:08 |
Dyrcona |
It the meetings move to Discord, I won't be there. I'm not kidding. |
| 15:08 |
abneiman |
JBoyer: can someone with the power to do so update the community calendar? |
| 15:09 |
JBoyer |
Dyrcona, I think the suggestion was 50/50 a joke, to make the community more attractive to the youths. |
| 15:09 |
stephengwills |
what’s a yoot? |
| 15:09 |
sandbergja |
meetings now moving to TikTok |
| 15:10 |
JBoyer |
At least reports would be quick, heh. |
| 15:10 |
terranm |
lol |
| 15:10 |
Dyrcona |
:) |
| 15:10 |
dluch |
lol |
| 15:10 |
berick |
2nd tuesday at 2 is the cataloging working group |
| 15:11 |
JBoyer |
Speaking of the calendar, I think Dyrcona has access, but it would be good to know who all does, and possibly expand that group if need be. |
| 15:11 |
sandbergja |
I think I have access |
| 15:11 |
terranm |
Were there people who didn't want to keep it first Tuesday afternoon? |
| 15:11 |
Dyrcona |
Yeah, I can edit the developer calendar and maybe the community calendar. |
| 15:11 |
phasefx |
we can always make an electron app for EG and have our meetings there :) |
| 15:12 |
JBoyer |
Well, 2pm, 3pm, AND 4pm all had the same number of votes, so we could do 3 instead. |
| 15:12 |
csharp |
phasefx++ |
| 15:12 |
terranm |
I think I can add things to the community calendar, but not edit other peoples' events |
| 15:12 |
phasefx |
(says the person who did embed chatzilla into the xul client once) |
| 15:12 |
Dyrcona |
:) |
| 15:13 |
Dyrcona |
Well, I suggested having a poll for new meeting time, because I thought we were getting a low turn out, particularly among core committers. |
| 15:13 |
terranm |
Ah |
| 15:13 |
abneiman |
noting that 2nd Tuesdays at 2pm is the typical time for Cataloging Working Group |
| 15:13 |
Dyrcona |
So, are we going with second tuesday at 3PM? |
| 15:13 |
sandbergja |
+1 to 3pm on 2nd tuesdays |
| 15:14 |
JBoyer |
I have typed and erased several messages. |
| 15:14 |
JBoyer |
I should just send smaller ones I suppose. |
| 15:15 |
JBoyer |
If there is no conflict with the second Tuesday at 3pm, lets do that. I'd really like to avoid 4 if possible. |
| 15:15 |
terranm |
+1 |
| 15:15 |
Bmagic |
#info Bmagic = Blake GH, MOBIUS |
| 15:15 |
gmcharlt |
+1 |
| 15:15 |
Dyrcona |
+1 |
| 15:15 |
berick |
+1 |
| 15:15 |
mmorgan |
+1 |
| 15:15 |
JBoyer |
#agreed Future meetings will take place on the second Tuesday of the month at 3pm Eastern time. |
| 15:16 |
JBoyer |
hurrah |
| 15:16 |
JBoyer |
So, on to the second action item from the last meeting, |
| 15:16 |
JBoyer |
2 sandbergja will put together a list of older bugs that need attention |
| 15:16 |
JBoyer |
#link http://list.evergreen-ils.org/pipermail/evergreen-dev/2021-January/000082.html And it was so. |
| 15:17 |
JBoyer |
sandbergja++ |
| 15:17 |
mmorgan |
sandbergja++ |
| 15:17 |
terranm |
sandbergja++ |
| 15:17 |
Dyrcona |
I have updated the calendar. Looks like it updated past meetings, too. |
| 15:17 |
Bmagic |
sandbergja++ |
| 15:17 |
mrisher |
Concerning those older bugs |
| 15:18 |
terranm |
I assume we won't be meeting next week tho? |
| 15:18 |
dluch |
sandbergja++ |
| 15:18 |
mrisher |
3 of them are ones that I'd like to follow up on. I'm going to be switching assignments in a few weeks, and at that point I won't be doing Evergreen work. I'd like to ask if anyone could please take a look at those 3 while I'm still doing Evergreen work. |
| 15:18 |
mrisher |
Maybe it can happen during feedback fest next week. |
| 15:19 |
JBoyer |
terranm, anyone can chat if they like but I'm not planning to do anything about next week myself. |
| 15:19 |
terranm |
mrisher: I'm so sorry to hear that :( |
| 15:19 |
sandbergja |
mrisher: oh man! We'll really miss you! |
| 15:19 |
mmorgan |
Indeed! |
| 15:19 |
JBoyer |
mrisher++ |
| 15:19 |
mrisher |
I'll miss you too!@ |
| 15:19 |
JBoyer |
Feedback fest is a good time. |
| 15:20 |
mrisher |
these are the 3: |
| 15:20 |
mrisher |
Needs discussion https://bugs.launchpad.net/evergreen/+bug/1848579 |
| 15:20 |
mrisher |
Needs testing https://bugs.launchpad.net/evergreen/+bug/1844169 , https://bugs.launchpad.net/evergreen/+bug/1847519 |
| 15:20 |
pinesol |
Launchpad bug 1848579 in Evergreen "Angular grids: interval columns are not filterable" [Medium,Confirmed] |
| 15:20 |
pinesol |
Launchpad bug 1844169 in Evergreen "Angular: Local Admin Search Filter Groups Port" [Wishlist,Confirmed] |
| 15:20 |
pinesol |
Launchpad bug 1847519 in Evergreen "Angular: Local Admin Circulation Limit Set Port" [Wishlist,Confirmed] |
| 15:20 |
sandbergja |
mrisher++ |
| 15:21 |
JBoyer |
In fact... I would suggest that anyone that can put together a test server (or 2) try to make sure that some of mmorgan's interesting / important bugs *and* some of sandbergja's old bugs are included, and mrisher's 3 because more Angular == more better. |
| 15:22 |
csharp |
Oldsquash week? |
| 15:22 |
JBoyer |
Not on every test server, of course, but I imagine there will be a handy worksheet like last time and we should try to make sure those are running *somewhere* |
| 15:22 |
dluch |
lol |
| 15:22 |
mmorgan |
Just a clarification on my list - those all have signoffs, do they need to have a place on a test server? |
| 15:23 |
JBoyer |
They do not! no one bother with mmorgan's list of bugs you don't need to load on a test server! :) |
| 15:23 |
mmorgan |
Just commit them!;-) |
| 15:23 |
JBoyer |
That also counts as feedback fest progress, yes. |
| 15:23 |
JBoyer |
Ok. |
| 15:24 |
csharp |
I do think it's worth the committer's time to test an older signed-off bug, but point taken |
| 15:24 |
Dyrcona |
I generally don't signoff and commit unless I've tested a bug fix. |
| 15:24 |
csharp |
same |
| 15:24 |
Dyrcona |
But, I suppose I could just commit ones that I've already tested. :) |
| 15:25 |
JBoyer |
csharp, certainly, but FF may allow for more in-depth testing, where a committer's testing usually involves knowing that it's already been given the once-over before they looked at it. |
| 15:26 |
mmorgan |
Make sense! I wasn't sure if committers built their own test enviroments for committing purposes. |
| 15:26 |
Dyrcona |
I'll see if I can make time to look at some of the signed off bugs this wek. |
| 15:26 |
|
mantis1 left #evergreen |
| 15:26 |
JBoyer |
I also assume committers do all of their testing directly rather than asking someone else to poke at things. |
| 15:26 |
mmorgan |
Dyrcona++ |
| 15:26 |
Dyrcona |
mmorgan: I think most of us do have our own test systems. |
| 15:26 |
JBoyer |
Moving on, we'll skip OpenSRF updates since there's nothing on the agenda, so up next is |
| 15:27 |
JBoyer |
#topic Evergreen Updates |
| 15:27 |
|
Topic for #evergreen is now Evergreen Updates (Meeting topic: 2020-02-02 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-02-02) |
| 15:27 |
JBoyer |
Feedback Fest discussion is basically part of this anyway, given the timing. :) |
| 15:28 |
berick |
for 3.7, next milestone is Feature Freeze -- 3 week countdown |
| 15:28 |
terranm |
I'm still in post-upgrade blues, so I'm behind on getting feedback fest testserver lists/info put together |
| 15:30 |
JBoyer |
#info 3.7 Feature Freeze is 2021-02-24 |
| 15:31 |
JBoyer |
terranm, any need to reschedule or just a little behind? |
| 15:31 |
terranm |
No, I'm just behind |
| 15:31 |
terranm |
I'll pull it together last minute |
| 15:31 |
JBoyer |
#info Feedback Fest is the week of 2021-02-08 |
| 15:31 |
JBoyer |
terranm++ |
| 15:32 |
mmorgan |
terranm++ |
| 15:32 |
gmcharlt |
terranm++ |
| 15:32 |
JBoyer |
#topic Security/point releases for 3.6.2, 3.5.3 and 3.4.6 on Wednesday, February 17, 2021. |
| 15:32 |
|
Topic for #evergreen is now Security/point releases for 3.6.2, 3.5.3 and 3.4.6 on Wednesday, February 17, 2021. (Meeting topic: 2020-02-02 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-02-02) |
| 15:32 |
dluch |
terranm++ |
| 15:32 |
terranm |
Bmagic: Are you willing to host a feedback fest test server next week? |
| 15:32 |
terranm |
We'll have two as well |
| 15:32 |
Bmagic |
sure! |
| 15:32 |
terranm |
Bmagic++ |
| 15:32 |
mmorgan |
Bmagic++ |
| 15:33 |
JBoyer |
No good way to "undo" with meetbot. |
| 15:33 |
terranm |
Sorry |
| 15:33 |
sandbergja |
terranm++ |
| 15:33 |
JBoyer |
Nope, you're fine. |
| 15:33 |
Dyrcona |
There are 3 security patches I want to roll into the point releases. IIRC, two of them are currently private. |
| 15:34 |
gmcharlt |
I can help with tarball creation tomorrow |
| 15:34 |
Dyrcona |
Well, we're not releasing until after feeback fest. |
| 15:34 |
gmcharlt |
ah, then I can help afterwards! |
| 15:35 |
gmcharlt |
(sorry, wasn't kidding about partial attention) |
| 15:35 |
Dyrcona |
At least, that's my suggestion from an email to the developer list. |
| 15:35 |
Dyrcona |
That's all right. I should be more prepared, I was digging out my car until just before the meeting. |
| 15:36 |
Bmagic |
Dyrcona++ combustion_engine_cars-- |
| 15:36 |
JBoyer |
Are all 3 already signed-off? I don't recall if a specific list of potential patches has been sent to the security list (I've been meaning to put one together myself and haven't yet.) |
| 15:36 |
Dyrcona |
Anyway, I'm requesting a commit moratorium from Noon EST on Tuesday, 2/16 until noon EST on Thursday 2/18 so that we can coordinate the mostly simultaneous release of the tarballs and announcement, etc. |
| 15:37 |
gmcharlt |
+1 |
| 15:37 |
Dyrcona |
JBoyer: I sent a list in December that was ignored. The three that I want to release are all signed off. |
| 15:39 |
Dyrcona |
They have also been targeted in Launchpad, so if you can see private bugs, you should be able to see them there. |
| 15:40 |
JBoyer |
I'll check that out. May have to double check my list settings too. |
| 15:40 |
JBoyer |
And +1 to the commit moratorium timeline. |
| 15:40 |
Dyrcona |
The list in December was a list of all of the security bugs, but I did say that for these three, I thought they were ready to go in. |
| 15:41 |
JBoyer |
Dyrcona++ |
| 15:42 |
JBoyer |
Any other point release discussion or questions about Evergreen updates before moving on? |
| 15:43 |
Dyrcona |
Well, I just want that there will be a 3.4.6 security release, and if my math is correct, it has two more months of security life. |
| 15:44 |
Dyrcona |
I also have some things I'd like reviewed during feedback fest, but I think we left that topic. :) |
| 15:45 |
JBoyer |
We don't need to review them today, so long as they're up next week! :D |
| 15:45 |
JBoyer |
But yes, I think you're right about 3.4.6 and the 3.4 timeline. |
| 15:46 |
JBoyer |
(don't need to review them all, that is) |
| 15:46 |
JBoyer |
#topic Documentation |
| 15:46 |
|
Topic for #evergreen is now Documentation (Meeting topic: 2020-02-02 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-02-02) |
| 15:46 |
JBoyer |
#info Next DIG meeting this Thursday, Feb. 4, and is on Zoom. Agenda: https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20210204-agenda |
| 15:47 |
JBoyer |
dluch, anything you'd like to add? |
| 15:47 |
dluch |
Nope! We didn't have a meeting in January, because just me and jihpringle showed up. :-D |
| 15:48 |
dluch |
Thanks! |
| 15:48 |
JBoyer |
dluch++ |
| 15:48 |
JBoyer |
#topic Launchpad Status |
| 15:48 |
|
Topic for #evergreen is now Launchpad Status (Meeting topic: 2020-02-02 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-02-02) |
| 15:48 |
JBoyer |
#info Open Bugs - 2527 |
| 15:49 |
JBoyer |
#info Pull Requests - 151 |
| 15:49 |
JBoyer |
#info Signoffs - 65 |
| 15:49 |
* mmorgan |
thought it would be useful to have a snapshot of the status of Launchpad bugs each meeting, so added that to the agenda. |
| 15:49 |
JBoyer |
Thank you to whoever pulled those together. |
| 15:49 |
JBoyer |
mmorgan++ |
| 15:49 |
terranm |
mmorgan++ |
| 15:49 |
JBoyer |
I agree! |
| 15:49 |
mmorgan |
Any other Launchpad stats that would be helpful? I'm happy to compile them. |
| 15:49 |
dluch |
mmorgan++ |
| 15:51 |
Dyrcona |
mmorgan++ |
| 15:51 |
Dyrcona |
I |
| 15:51 |
terranm |
Maybe number of new bugs added since previous meeting? |
| 15:52 |
Dyrcona |
When you're testing the branch on a Lp bug, please assign the bug to yourself. |
| 15:52 |
mmorgan |
terranm: Good idea! |
| 15:52 |
terranm |
Likewise, number of signoffs and pullrequests added since previous meeting? |
| 15:52 |
mrisher |
terranm++ |
| 15:53 |
terranm |
And number of commits... you get the idea :D |
| 15:53 |
terranm |
mmorgan++ |
| 15:53 |
* mmorgan |
gets the idea! |
| 15:53 |
Dyrcona |
mmorgan: How are you getting these statistics? Are you tracking them yourself or using the Lp API? |
| 15:53 |
JBoyer |
I think a visual indicator of progress like that would be helpful. |
| 15:53 |
mmorgan |
terranm++ |
| 15:54 |
mmorgan |
Dyrcona: For this first snapshot, just using Launchpad search. |
| 15:54 |
mmorgan |
Open bugs are what Launchpad reports on the main screen. |
| 15:55 |
mmorgan |
pullrequest have that tag, but are not signedoff |
| 15:55 |
mmorgan |
signedoff have that tag, but are not committed. |
| 15:56 |
Dyrcona |
OK. I get the idea. :) I might look into using the APIs again for things. Seems like every time I get something working, they change the back end, and I have to start over or upgrade my Ubuntu. :) |
| 15:57 |
Dyrcona |
It looks like we're never leaving Lp at this rate. :) |
| 15:57 |
jeffdavis |
Or we could just close all existing bugs. |
| 15:57 |
jeffdavis |
"moved to new bug tracker, didn't fix" |
| 15:58 |
terranm |
heh |
| 15:59 |
stephengwills |
wait until mmorgan has the workflows for all the new stats debugged first. |
| 15:59 |
phasefx |
we've done that before |
| 15:59 |
terranm |
Or we could just fix all of - 2500 bugs shouldn't be that hard, right? |
| 15:59 |
phasefx |
(RIP Bugzilla) |
| 15:59 |
jeff |
twice now. |
| 16:00 |
phasefx |
(and TRAC) |
| 16:00 |
terranm |
There's probably, like, 10 of them I could fix |
| 16:00 |
* mmorgan |
bets many of those bugs no longer need to be fixed. |
| 16:00 |
Dyrcona |
terranm: Go for it! |
| 16:01 |
terranm |
I'll leave a few for the rest of you |
| 16:01 |
mmorgan |
:) |
| 16:01 |
JBoyer |
Launchpad janitorial work is still helping out, if anyone has time to look at a small subset of 2500+ bugs and determine that some don't apply anymore. |
| 16:03 |
alynn26 |
maybe the new dev group can look at some of the bugs that have been around for a while that checking on. May be make it a meeting. |
| 16:03 |
JBoyer |
And it seems like discussions about changing bug tracking systems (again) seem to do best in person. But, 20 people answered my poll and 18 said that specific combination of times worked for them, so if anyone wants to throw it on the agenda for March and see what happens, that's an option. ;) |
| 16:04 |
terranm |
alynn26: good idea, I'll put that on this month's agenda |
| 16:04 |
JBoyer |
terranm++ |
| 16:04 |
JBoyer |
alynn26++ |
| 16:04 |
dluch |
DIG has also talked about (and done some) reviewing of old bugs with the documentation label |
| 16:04 |
alynn26 |
I'll get you a list of possible bugs |
| 16:04 |
Dyrcona |
alynn26++ # That sounds like a capital idea! |
| 16:04 |
terranm |
alynn26++ |
| 16:04 |
mmorgan |
alynn26++ |
| 16:05 |
dluch |
alynn26++ |
| 16:05 |
mrisher |
re: "documentation label" |
| 16:05 |
mrisher |
Is there a LP tag "documentation"? |
| 16:06 |
alynn26 |
yes |
| 16:06 |
dluch |
yep |
| 16:06 |
mrisher |
I do know of a bug that needs documentation help, so I should tag it appropriately |
| 16:06 |
dluch |
Definitely! Thanks |
| 16:06 |
mrisher |
never knew that was a tag til now |
| 16:07 |
JBoyer |
Any other LP discussion before I move us quickly to new business and talk about LP real quick? |
| 16:08 |
terranm |
mrisher: This list has the 'official' tags and their usage guidelines |
| 16:08 |
terranm |
https://wiki.evergreen-ils.org/doku.php?id=dev:lp_tags |
| 16:08 |
mrisher |
terranm: that's useful! thank you |
| 16:08 |
Dyrcona |
You can also start typing in the tag box, and it will suggest existing tags. That works in search, too, I think. |
| 16:08 |
JBoyer |
"official" also having the benefit of auto-completion in LP. |
| 16:09 |
JBoyer |
Ok, going to move on because I |
| 16:09 |
JBoyer |
've kept people longer than expected |
| 16:09 |
JBoyer |
#info New Business |
| 16:09 |
JBoyer |
#topic New Business |
| 16:09 |
|
Topic for #evergreen is now New Business (Meeting topic: 2020-02-02 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-02-02) |
| 16:09 |
JBoyer |
#info LP 1914116 - Query string cleanup after fixing LP 1687545 |
| 16:09 |
pinesol |
Launchpad bug 1914116 in Evergreen "An audit of query parameters is needed" [Critical,New] https://launchpad.net/bugs/1914116 |
| 16:09 |
pinesol |
Launchpad bug 1687545 in Evergreen "W3C wants query parameters standardized on ampersands; semicolons are now bad" [Medium,Fix committed] https://launchpad.net/bugs/1687545 |
| 16:10 |
JBoyer |
545 has finally banished the semicolons from our query strings, but now we need to fix mkurl because param©_count becomes param(c)_count, which while amusing, does not work. |
| 16:11 |
JBoyer |
So I just wanted to bring that up because point releases (except 3.4.6) will include 545 and should have a fix for 116. |
| 16:12 |
JBoyer |
#topic Announcements |
| 16:12 |
|
Topic for #evergreen is now Announcements (Meeting topic: 2020-02-02 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-02-02) |
| 16:12 |
JBoyer |
#info Next Meeting is 2021-03-09 at 3pm Eastern / 12 Pacific |
| 16:12 |
JBoyer |
I believe that's it. |
| 16:12 |
JBoyer |
#endmeeting. |
| 16:12 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |
| 16:12 |
pinesol |
Meeting ended Tue Feb 2 16:12:30 2021 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:12 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-02-02-15.02.html |
| 16:12 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-02-02-15.02.txt |
| 16:12 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-02-02-15.02.log.html |
| 16:12 |
JBoyer |
Thanks everyone |
| 16:12 |
terranm |
JBoyer++ |
| 16:12 |
mmorgan |
JBoyer++ |
| 16:12 |
mrisher |
JBoyer++ |
| 16:12 |
mrisher |
thanks |
| 16:12 |
sandbergja |
JBoyer++ |
| 16:12 |
Dyrcona |
JBoyer++ |
| 16:13 |
Dyrcona |
Also, I think the calendar is now fixed. |
| 16:13 |
Dyrcona |
It looks right on my phone and in the Thunderbird calendar extension. |
| 16:14 |
JBoyer |
Dyrcona++ |
| 16:16 |
berick |
JBoyer++ |
| 16:17 |
csharp |
JBoyer++ |
| 16:18 |
jeffdavis |
Is the query param issue largely fixable by modifying the mkurl macro? Or do the changes likely need to be made in situ where URLs appear in templates? |
| 16:19 |
mrisher |
dluch: this is the bug I mentioned that needs documentation. I just added the appropriate tag. https://bugs.launchpad.net/evergreen/+bug/998080 |
| 16:19 |
pinesol |
Launchpad bug 998080 in Evergreen "Circ, Hold Matrix Weights interface especially difficult to use" [Wishlist,Triaged] |
| 16:19 |
dluch |
JBoyer++ |
| 16:20 |
JBoyer |
jeffdavis, I'm hoping just by modifying mkurl, but haven't looked closely enough at it. |
| 16:28 |
mmorgan |
sandbergja: Re bug 1908135 and its friends. Is this a situation where a single change will show up on all the pages with the org selector? |
| 16:28 |
pinesol |
Launchpad bug 1908135 in Evergreen "Angular org unit selector always defaults to the consortium with no ancestors or descendants selected" [Undecided,New] https://launchpad.net/bugs/1908135 |
| 16:29 |
|
sandbergja_ joined #evergreen |
| 16:31 |
JBoyer |
Some of those "common controls" (Hi from my visual basic past) may allow you to specify that this or that is set by default on a page-by-page basis. If the org selector works that way (haven't checked yet) then it would be easy to change one page without any others changing. And if it doesn't, that would be a great addition! :) |
| 16:33 |
* mmorgan |
was hoping it would change the behavior everywhere, our users are used to the client knowing where they are, and now they have to tell it every time they visit each screen. |
| 16:36 |
dluch |
mrisher: great, thanks! |
| 16:42 |
JBoyer |
mmorgan, also possible, I should have read the bug before mentioning how something could work. :) (and yes, defaulting to your workstation OU would be a good enhacement) |
| 16:43 |
Bmagic |
It's as if millions of bugs all cried out at once, and were silenced. You keep practicing. |
| 16:44 |
mmorgan |
JBoyer: I don't really see it as an enhancement. Feels more like a regression. |
| 16:46 |
JBoyer |
True, was a bit loose with my terminology there. It's a bug fix that would enhance many people's experience. :) |
| 16:46 |
mmorgan |
Exactly! |
| 16:48 |
Dyrcona |
I can think of a couple of bugs that ought to be turned into questions. |
| 17:02 |
|
mrisher joined #evergreen |
| 17:18 |
|
mmorgan left #evergreen |
| 17:57 |
|
sandbergja_ joined #evergreen |
| 18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 20:22 |
|
stephengwills left #evergreen |
