Timestamps are in GMT/BST.
[6:37] -leguin.freenode.net- *** Looking up your hostname...
[6:37] -leguin.freenode.net- *** Checking Ident
[6:37] -leguin.freenode.net- *** Found your hostname
[6:37] -leguin.freenode.net- *** No Ident response
[6:37] * DuraLogBot (~PircBot@webster.duraspace.org) has joined #duraspace
[6:37] * Topic is 'Welcome to DuraSpace IRC. This channel is used for formal meetings and is logged - http://irclogs.duraspace.org/'
[6:37] * Set by tdonohue on Thu Sep 15 17:49:38 UTC 2016
[11:34] * tdonohue (~tdonohue@dspace/tdonohue) has joined #duraspace
[12:01] * mhwood (~mhwood@mhw.ulib.iupui.edu) has joined #duraspace
[13:45] * mhwood (~mhwood@mhw.ulib.iupui.edu) Quit (Remote host closed the connection)
[14:07] * mhwood (~mhwood@mhw.ulib.iupui.edu) has joined #duraspace
[14:41] <DSpaceSlackBot1> <tdonohue> <here>: our DSpace Developers Meeting starts at the top of the hour (~20mins). Today's agenda is posted at https://wiki.duraspace.org/display/DSPACE/DevMtg+2018-06-13 (And it includes links to various slides/workshops from OR2018)
[14:41] <kompewter> [ DevMtg 2018-06-13 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2018-06-13
[15:00] <DSpaceSlackBot1> <tdonohue> <here>: It's DSpace DevMtg time! Let's do a quick roll call to see who is able to join today.
[15:00] <DSpaceSlackBot1> <jcreel256> hi
[15:02] <DSpaceSlackBot1> <tdonohue> Well, it might be a rather short meeting if it's just the two of us, @jcreel256 ;)
[15:02] <DSpaceSlackBot1> <mwood> Hi
[15:02] <DSpaceSlackBot1> <tdonohue> I do know that several folks are at other conferences this week or on vacation, so I'm not surprised attendance is low today
[15:02] <DSpaceSlackBot1> <tdonohue> Hi @mwood
[15:03] <DSpaceSlackBot1> <tdonohue> Ok, we'll go ahead and get started. Still may be a rather short meeting, but we'll see if others are able to join in along the way.
[15:04] <DSpaceSlackBot1> <tdonohue> For topic #1 on the agenda, I added in a series of links to all the major DSpace talks/workshops (mostly around DSpace 7) from OR2018. https://wiki.duraspace.org/display/DSPACE/DevMtg+2018-06-13
[15:04] <kompewter> [ DevMtg 2018-06-13 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2018-06-13
[15:05] <DSpaceSlackBot1> <tdonohue> There will also be a OR2018 summary email going out to all lists with this info (sometime this week). It's waiting on me to record the DSpace 7 demo that I did live at OR2018 (as part of the DSpace 7 update talk). Once I get that demo recorded (which was a big part of that talk), I'll be sending these out to everyone
[15:05] <DSpaceSlackBot1> <terrywbrady> here
[15:06] <DSpaceSlackBot1> <tdonohue> Overall, the feedback I heard from OR2018 was very positive. The DSpace 7 demo got a lot of smiles (and later "congrats, it's looking amazing" comments from several folks). So, I think we've succeeded in generating some good excitement around DSpace 7 -- and hopefully we can carry that over to our mailing list ;)
[15:07] <DSpaceSlackBot1> <tdonohue> DSpace 7 Workshops were also well attended (I counted about 30-40 in each)
[15:08] <DSpaceSlackBot1> <tdonohue> Not sure if anyone else who attended OR2018 (@terrywbrady or @mwood) has more to share? I also know we have a Dev Show & Tell coming up on June 26 to talk OR2018, etc
[15:09] <DSpaceSlackBot1> <terrywbrady> I agree. It was a great meeting. I heard from a couple folks who may be interested in a future Sprint.
[15:09] <DSpaceSlackBot1> <mwood> It seemed there were a lot of sessions about dataset repositories. The topic is heating up.
[15:10] <DSpaceSlackBot1> <tdonohue> Yes, we did a lot of promotion of the next DSpace 7 Sprint (July 9-20), so I'm also hoping we'll get some sprinters out of it! https://wiki.duraspace.org/display/DSPACE/DSpace+7+Community+Sprints
[15:10] <kompewter> [ DSpace 7 Community Sprints - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DSpace+7+Community+Sprints
[15:10] <DSpaceSlackBot1> <terrywbrady> It was good to see many familiar folks. I was also surprised to hear from institutions using DSpace who do not regularly attend this meeting or DCAT. It gave me a better sense of the depth of the community.
[15:11] <DSpaceSlackBot1> <tdonohue> I should also note that at OR2018 there was a fair amount of discussion of COAR's Next Generation Repositories report: http://ngr.coar-repositories.org/ It's worth getting familiar with, and DSpace 7 will be adding two new technologies (ResourceSync & Signposting) to align with the recommendations out of that report
[15:11] <kompewter> [ COAR Next Generation Repositories: Vision and Objectives ] - http://ngr.coar-repositories.org/
[15:11] <DSpaceSlackBot1> <terrywbrady> At the show and tell meeting, I am also going to encourage conference speakers to summarize and re-post links to their talks.
[15:12] <DSpaceSlackBot1> <tdonohue> ResourceSync: http://www.openarchives.org/rs
[15:12] <kompewter> [ ResourceSync Framework Specification - Table of Contents ] - http://www.openarchives.org/rs
[15:12] <DSpaceSlackBot1> <tdonohue> Signposting: http://signposting.org/
[15:12] <kompewter> [ Signposting the Scholarly Web ] - http://signposting.org/
[15:13] <DSpaceSlackBot1> <tdonohue> So, it sounds like we'll have the opportunity to dig a little deeper in the upcoming Dev Show & Tell, which is good. Any last notes / concepts to share / link to?
[15:14] <DSpaceSlackBot1> <mwood> I need to transcribe my notes while I can still understand them.
[15:14] <DSpaceSlackBot1> <terrywbrady> For the July Show and Tell, I would love to find another presenter who is a power user of Postman. If you all know of anyone who might be good to ask, let me know.
[15:15] <DSpaceSlackBot1> <tdonohue> @terrywbrady: Even a non-power user of Postman could be useful. I know it was part of the REST API Workshop at OR2018, but keep in mind that it's still likely a very new tool to most DSpace Devs.... so, a basic intro could also be of use for that Show & Tell
[15:16] <DSpaceSlackBot1> <terrywbrady> Good point. We can re-use some of the workshop steps for that purpose.
[15:16] <DSpaceSlackBot1> <tdonohue> :+1: exactly
[15:17] <DSpaceSlackBot1> <terrywbrady> And I would love to do a Spring overview at a future meeting...
[15:18] <DSpaceSlackBot1> <tdonohue> "Spring" is a bit broad, to be honest (there are so many Spring-related tools, etc). But, I think it would be useful to have a future meeting on how Spring is being used *in the new REST API* (again, some of the workshop stuff could be useful). As I think that's the newest area of interest
[15:19] <DSpaceSlackBot1> <tdonohue> So, I like the idea, but we likely need to scoped to how specific areas of DSpace use Spring (cause there's a lot of stuff in Spring that we *don't* use)
[15:20] <DSpaceSlackBot1> <tdonohue> In any case, moving along here...I think we have the basics from OR2018 covered!
[15:20] <DSpaceSlackBot1> <terrywbrady> sounds good
[15:21] <DSpaceSlackBot1> <tdonohue> DSpace 7 updates -- there's nothing much to share here, as all the recent effort went into prepping for OR2018 and the "live demo" there. Again, I'll be recording the demo & putting it up on YouTube this week, for anyone who missed it.
[15:21] <DSpaceSlackBot1> <tdonohue> Also, it's worth noting, we will NOT be having a DSpace 7 Meeting tomorrow (normally it's every Thurs at 14UTC)
[15:22] <DSpaceSlackBot1> <tdonohue> Both Andrea B & Art L are out this week, so I'd expect attendance to be low...plus, my week has turned more hectic than expected. So, any DSpace 7 updates should be shared on Slack (and I noted such on angular-ui and rest-api channels)
[15:23] <DSpaceSlackBot1> <tdonohue> Moving along to DSpace 6.3 updates... @kshepherd kindly shared updates in the Agenda (under bullet #3).
[15:23] <DSpaceSlackBot1> <tdonohue> 6.3 is almost "closed". There's only one PR that is still open under the 6.3 milestone: https://github.com/DSpace/DSpace/pull/1999
[15:23] <kompewter> [ DS-3870 S3 bitstore leaves connections to AWS open by benbosman · Pull Request #1999 · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pull/1999
[15:24] <DSpaceSlackBot1> <tdonohue> This PR has been highlighted as fixing a major issue with the S3 assetstore implementation.
[15:24] <DSpaceSlackBot1> <tdonohue> As Ben Bosman notes (in PR comments), it's been in production for 3 months. He thinks it's ready to go, but really just wants more eyes on it
[15:25] <DSpaceSlackBot1> <tdonohue> I don't imagine anyone <here> uses S3 regularly, and would have time/interest in testing this PR? Otherwise, we may need to consider relying on trust & just doing a code review
[15:26] <DSpaceSlackBot1> <terrywbrady> I am out the rest of this week and have some projects to catch up on. I can help to re-test 6.3 once it is created. Otherwise, my time will be limited.
[15:27] <DSpaceSlackBot1> <mwood> No S3 use here....
[15:27] <DSpaceSlackBot1> <terrywbrady> Not here either
[15:27] <DSpaceSlackBot1> <jcreel256> nor us
[15:28] <DSpaceSlackBot1> <tdonohue> Ok, well is anyone here willing to help me do a code review of PR#1999? Obviously Ben is a trusted committer, and it's good to know it is used in Production. Maybe we just let this through via code review, as it's gonna be "better than nothing"
[15:29] <DSpaceSlackBot1> <tdonohue> In any case, I'll give this a code review this week....and we'll also see what @kshepherd thinks. My gut says this seems fine for a 6.3, but want to be sure others agree
[15:30] <DSpaceSlackBot1> <mwood> I've been looking it over, but the diff doesn't give enough context to understand it. Gotta just go read the whole thing.
[15:31] <DSpaceSlackBot1> <tdonohue> Yes, I think that's accurate, @mwood. There's a bit of refactoring here that doesn't necessarily make complete sense in the diff...but I'm assuming it would when looking at the overall code logic. So, I'm in the same boat...need to find 20-30mins to dig in and understand this class more
[15:31] <DSpaceSlackBot1> <tdonohue> In any case, I've assigned myself as a reviewer of the PR. Will get to it this week.
[15:32] <DSpaceSlackBot1> <tdonohue> @kshepherd also noted in the agenda that he shared a draft of the 6.3 Release Notes / Announcement with Committers (this was just before OR2018). So, I'd encourage Committers (here or reading later) to read that and give feedback (even just +1's).
[15:33] <DSpaceSlackBot1> <tdonohue> I admit, this is another TODO for me too...I didn't have time to look at that draft myself, but will ;)
[15:35] <DSpaceSlackBot1> <tdonohue> Also, as noted by @kshepherd we could use some backporting / forward porting help here. I know we have a number of closed PRs with the "port to master" label. We need some help simply porting these all to `master` to ensure the bug is fixed there too
[15:35] <DSpaceSlackBot1> <tdonohue> https://github.com/DSpace/DSpace/pulls?q=is%3Apr+label%3A%22port+to+master%22+is%3Aclosed
[15:35] <kompewter> [ Pull Requests · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pulls?q=is%3Apr+label%3A%22port+to+master%22+is%3Aclosed
[15:35] <DSpaceSlackBot1> <tdonohue> Once a PR is ported to `master` and merged, we should remove that label from the old PR. This just ensures we know which PRs haven't yet been "synced" between branches
[15:36] <DSpaceSlackBot1> <tdonohue> Similarly, it looks like we have one PR with the "port to 6.x" label: https://github.com/DSpace/DSpace/pulls?q=is%3Apr+label%3A%22port+to+6.x%22+is%3Aclosed
[15:36] <kompewter> [ Pull Requests · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pulls?q=is%3Apr+label%3A%22port+to+6.x%22+is%3Aclosed
[15:37] <DSpaceSlackBot1> <tdonohue> @mwood: has https://github.com/DSpace/DSpace/pull/2032 been ported to 6.x (for 6.3)? Do we need to get this done ASAP?
[15:37] <kompewter> [ [DS-3795] Update jackson-databind due to known vulnerabilities. by mwoodiupui · Pull Request #2032 · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pull/2032
[15:37] * misilot (~misilot@p-body.lib.fit.edu) Quit (Read error: Connection reset by peer)
[15:38] <DSpaceSlackBot1> <tdonohue> Or do we feel this should not yet be ported to 6.x? Just wanting to understand why we have this label applied and whether it should be removed or resolved
[15:38] <DSpaceSlackBot1> <mwood> I'm trying to figure that out....
[15:39] <DSpaceSlackBot1> <tdonohue> Looks like @kshepherd added the label. Maybe it's worth analyzing if this can be simply ported to 6.x (for 6.3)? Is that something you could do this week, @mwood?
[15:39] <DSpaceSlackBot1> <mwood> I will look into it.
[15:39] <DSpaceSlackBot1> <tdonohue> If it's not a simple/clean port, I'd say we leave it out of 6.3.
[15:40] <DSpaceSlackBot1> <tdonohue> In any case, as you all can tell, there's a lot of porting effort that we could use help for (either leading up to 6.3 or just afterwards). So, anyone with free time could really help out by selecting a PR with a "port to master" label and creating a new PR that makes the same changes on `master`.
[15:41] <DSpaceSlackBot1> <tdonohue> It's not a flashy task, but it's necessary...and it'll get done faster if we all can chip in a little
[15:41] <DSpaceSlackBot1> <tdonohue> (And I'll gladly volunteer to review any such ported PRs and merge quickly. Just assign me as a reviewer or ping me via Slack)
[15:42] <DSpaceSlackBot1> <mwood> Noted.
[15:43] <DSpaceSlackBot1> <tdonohue> Also, there's one more semi-major 5.x ticket that is open, has recommended workarounds (in comments) but simply needs a PR. As we will be releasing a 5.9 (alongside 6.3, to backport a few major fixes), this is the last opportunity to get this annoying bug fixed: https://jira.duraspace.org/browse/DS-3649
[15:43] <kompewter> [ [DS-3649] no longer can select eperson after upgrade to 5.6 - DuraSpace JIRA ] - https://jira.duraspace.org/browse/DS-3649
[15:44] <kompewter> [ https://jira.duraspace.org/browse/DS-3649 ] - [DS-3649] no longer can select eperson after upgrade to 5.6 - DuraSpace JIRA
[15:45] <DSpaceSlackBot1> <tdonohue> If anyone here is annoyed by this bug, I'd recommend taking a look at that ticket...this comment summarizes the proposed fix: https://jira.duraspace.org/browse/DS-3649?focusedCommentId=58092&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-58092
[15:45] <kompewter> [ [DS-3649] no longer can select eperson after upgrade to 5.6 - DuraSpace JIRA ] - https://jira.duraspace.org/browse/DS-3649?focusedCommentId=58092&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-58092
[15:45] <kompewter> [ https://jira.duraspace.org/browse/DS-3649 ] - [DS-3649] no longer can select eperson after upgrade to 5.6 - DuraSpace JIRA
[15:45] <DSpaceSlackBot1> <tdonohue> I think it's pretty quick, just a few lines...but I've not had a chance to verify on my end, or create a PR. If anyone could find time to do this, it'd be a huge help.
[15:46] <DSpaceSlackBot1> <mwood> I may have time to take a look at it.
[15:46] <DSpaceSlackBot1> <tdonohue> Thanks, @mwood! It seems like it should be relatively easy to reproduce. The fix seems like a possible two-liner. I'm glad to review this as needed too.
[15:48] <DSpaceSlackBot1> <tdonohue> I think that's all I have for today's agenda. Obviously there's a few things left to push forward here (hopefully very quickly) to get 6.3 and 5.9 out the door. I'll try and touch base with @kshepherd later today/tomorrow to see how I can help
[15:48] <DSpaceSlackBot1> <tdonohue> My week so far has been busy, but there's "light at the end of the tunnel", so I'm hoping I'll have some more time to help move this forward quickly later this week and early next week
[15:49] <DSpaceSlackBot1> <tdonohue> Any last thoughts / comments / questions to share here from anyone (about any topics from today)?
[15:50] <DSpaceSlackBot1> <tdonohue> Not hearing anything. Thanks all, and please do help us get this release finished up / out the door! I think we are nearly there, but just a few tasks remain to close it up & get it out there!
[15:51] <DSpaceSlackBot1> <tdonohue> We'll close the meeting for today. As always, I'm available on Slack if things come up. So we'll touch base via Slack & at next week's meeting.
[16:35] * tdonohue (~tdonohue@dspace/tdonohue) has left #duraspace
[20:31] * ogres (uid159312@gateway/web/irccloud.com/x-pgfgkdyvqioajccl) has joined #duraspace
[21:26] * mhwood (~mhwood@mhw.ulib.iupui.edu) Quit (Remote host closed the connection)
These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.